Re: Assembly plugin plugin
The latter. There is indeed a 'root' module with a pluginManagement section. I do not control its content directly, I can ask that the my assembly plugin be added there. Thanks On Tue, Apr 17, 2012 at 11:39 PM, Wayne Fay wayne...@gmail.com wrote: I suppose I will have to figure out a way to make sure mine gets loaded first. Are there any tricks out there for fooling the reactor? I know of no tricks. You should talk to the owner of the other module(s) using the assembly plugin and convince them to add your handler into their plugindependencies or even better get the owner of the top parent to add a pluginManagement section and specify it there (then it will be inherited down to all the other poms). Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Assembly plugin plugin
I have written a ContainerDescriptorHandler plugin for the Maven assembly plugin. It works when the module that uses it is built 'standalone'. When the module is built as part of a large multi-module project I see either [INFO] : org.apache.maven.plugin.assembly.model.Assembly@13579e0 Assembly is incorrectly configured: null Assembly: null is not configured correctly: Cannot find ContainerDescriptorHandler with hint: instructions Or, even worse, [INFO] Trace java.lang.OutOfMemoryError: Java heap space at java.lang.String.substring(String.java:1770) at org.codehaus.plexus.interpolation.util.StringUtils.capitalizeFirstLetter(StringUtils.java:119) at org.codehaus.plexus.interpolation.reflection.ReflectionValueExtractor.evaluate(ReflectionValueExtractor.java:90) at org.codehaus.plexus.interpolation.ObjectBasedValueSource.getValue(ObjectBasedValueSource.java:59) at org.codehaus.plexus.interpolation.PrefixedValueSourceWrapper.getValue(PrefixedValueSourceWrapper.java:134) at org.codehaus.plexus.interpolation.AbstractDelegatingValueSource.getValue(AbstractDelegatingValueSource.java:44) at org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:196) at org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:124) at org.apache.maven.project.interpolation.AbstractStringBasedModelInterpolator.interpolateInternal(AbstractStringBasedModelInterpolator.java:315) at org.apache.maven.project.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.traverseObjectWithParents(StringSearchModelInterpolator.java:185) at org.apache.maven.project.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.run(StringSearchModelInterpolator.java:135) at org.apache.maven.project.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.run(StringSearchModelInterpolator.java:102) at java.security.AccessController.doPrivileged(Native Method) at org.apache.maven.project.interpolation.StringSearchModelInterpolator.interpolateObject(StringSearchModelInterpolator.java:80) at org.apache.maven.project.interpolation.StringSearchModelInterpolator.interpolate(StringSearchModelInterpolator.java:62) at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:990) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:880) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:255) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:163) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedArtifact(MavenMetadataSource.java:94) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:387) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:435) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:435) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:316) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1499) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) I have boosted the memory settings to ridiculously high values with no effect, which leads me to believe I have created some kind of infinite dependency loop, because many of the other modules also use the assembly plugin (although without my ContainerDescriptorHandler). Does Maven have a switch to log the workings of the dependency mechanism as it does its job?
Re: Assembly plugin plugin
M2. I suppose I will have to figure out a way to make sure mine gets loaded first. Are there any tricks out there for fooling the reactor? On Tue, Apr 17, 2012 at 5:58 PM, Jörg Schaible joerg.schai...@gmx.dewrote: Robert Egan wrote: I have written a ContainerDescriptorHandler plugin for the Maven assembly plugin. It works when the module that uses it is built 'standalone'. When the module is built as part of a large multi-module project I see either Does Maven have a switch to log the workings of the dependency mechanism as it does its job? M2 or M3? For M2 the first error is normal, since every plugin is loaded once and once only. If the first usage of the assembly plugin does not contain your handler as part of its classpath, it will not be available anywhere else in the multi-project build. M3 should instantiate the plugin again with the proper CP. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
module question
I have a POM hat works correctly when it is the 'root' POM but fails to resolve a dependency when it is invoked as a module from another POM. How does one go about resolving an issue like this?
Re: module question
Thanks The real answer is that in the multi-module project, someone calls the 'standard' assembly plugin before I do (there are many other EARs, WARs and JARs in the build). So it is the one in memory when the module that needs mine is invoked. I need to find a way to insure that my assembly plugin is loaded first, and therefore loads the required dependency. On Tue, Apr 17, 2012 at 7:25 PM, Stevo Slavić ssla...@gmail.com wrote: Hello Robert, My guess is that the other pom defines a repository which cannot be accessed (e.g. due to security constraints). Having failing build output, not to mention pom files themselves, would help a lot to better diagnose root cause. Regards, Stevo. On Apr 18, 2012 1:17 AM, Robert Egan robert.e...@aciworldwide.com wrote: I have a POM hat works correctly when it is the 'root' POM but fails to resolve a dependency when it is invoked as a module from another POM. How does one go about resolving an issue like this?
Re: module question
Thanks But that's not my decision to make. On Tue, Apr 17, 2012 at 9:38 PM, Wayne Fay wayne...@gmail.com wrote: The real answer is that in the multi-module project, someone calls the 'standard' assembly plugin before I do (there are many other EARs, WARs and JARs in the build). So it is the one in memory when the module that needs mine is invoked. I need to find a way to insure that my assembly plugin is loaded first, and therefore loads the required dependency. Or you could just move to Maven3 where this bug in M2 was resolved... assuming that I understand what you are saying. Otherwise if you are on M3, you need to adjust your dependencies and declare things in such a way that Maven can properly calculate the build path. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [SURVEY] How does your team retrieve artifacts?
We use HTTP. Hi, I'm just trying to get some data on what protocol is used to retrieve artifacts. This question strictly relates to what you use for retrieval. Most people I have seen use a web server or a shared network drive, but I'd like to get some feedback. [ ] Our team uses HTTP to retrieve our artifacts [ ] Our team intends to use HTTP to retrieve our artifacts [ ] Our team uses the filesystem [ ] Our team does not use HTTP or the filesystem because please say what protocol you use and the reason Thanks, Jason --- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: maven2 was plugin
You must use the plugin on a machine where Websphere is installed, but you can deploy TO any machine running websphere by setting the configuration parameters of host, port,username and password. Robert Egan Guillaume Boucherie [EMAIL PROTECTED] wrote on 05/05/2008 09:23:17 AM: Hi all, I'm trying to find a maven2 plugin for was. I'm want to be able to deploy an ear on a remote websphere. I'm trying the was6 maven plugin from codehaus http://mojo.codehaus.org/was6-maven-plugin/index.html But with this plugin I must run maven on the same machine where websphere is install. Does anybody know a plugin that do this work ? Thanks This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Remote file copy
I have a need to implement Maven style deploy functionality (copy files to multiple remote servers as defined in an xml file on the source machine). Attempts to find something using google have been unsuccessful, mostly due to the generality of the query. What other Apache projects might be best suited for this task? Thanks Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
RE: deleting things out of a repository
This is a very valid scenario and one that I need to address before I formally replace our Ant build with Maven. The build currently runs about 600Mb before it's done and will (fairly) quickly exhaust the diskspace on our build machine. Even today, the last thing we do is archive the complete build and move it offline, to make room for the next one. What I had thought I might to is to tweak the settings xml so that a single release build went to it's own repository folder structure, say ~/.m2/b20080331-123046. Then the cleanup is a simple rmdir. Does that seem like a plausible answer? Robert Egan EJ Ciramella [EMAIL PROTECTED] wrote on 03/31/2008 01:29:56 PM: Pretend for a moment maven will still be in use in 10 years - you will truly keep around something generated today? Additionally, that's just repo1, what about people managing their own repositories? For organizations managing a live site, a jar artifact or set of web binaries from a year ago are typically useless as they have been updated maybe 100 times since the original install. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2008 12:44 PM To: Maven Users List Subject: Re: deleting things out of a repository Almost by definition, Maven does not support undeploy. That would imply that the repo is not write-once but rather changeable. While this is acceptable for SNAPSHOTs, it is not acceptable for releases. So, I think you'll have to do this manually. I just don't see this EVER making it into a core Maven plugin, for good reasons. Wayne On 3/31/08, EJ Ciramella [EMAIL PROTECTED] wrote: Well, we manage a live site so artifacts released a month ago are more often than not, useless cruft. We don't have a snapshot repository (just yet) so that isn't a problem (just yet). But I don't want to go in with a sword and start chopping out bits when there is data about said bits everywhere (in the metadata files). It'd be great if there was a mvn undeploy groupId:artifactId: version type command. Or if the deploy or release plugins would be configurable to say, purge stuf X days old or something. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tamás Cservenák Sent: Sunday, March 30, 2008 6:23 PM To: Maven Users List Subject: Re: deleting things out of a repository And not to mention the recipe that remote repo (even those inhouse, locally managed ones [probably hosted by one of MRMs or even web server]) should only advance forward in time and _have_no_artifact_deleted_. Exception for those are SNAPSHOTs, as Wendy said. ~t~ On Sun, Mar 30, 2008 at 10:42 PM, Wendy Smoak [EMAIL PROTECTED] wrote: On Sun, Mar 30, 2008 at 1:41 PM, EJ Ciramella [EMAIL PROTECTED] wrote: What's the best way to remove, say, 10 or so old builds out of the repository (a locally run/managed one)? is there a mvn undeploy command? Can you explain more about what you're looking for? Are these snapshots or releases? (And is this a remote repository, or ~/.m2/repository?) Two things that come to mind are Apache Archiva's ability to purge snapshots from the repos it manages, and the recent discussions of the need for a tool to keep the local repo size under control. -- Wendy -- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: Logging
You're right. AbstractMojo creates it's own Log interface based on System.out. It would be nice if it at least attempted to find the plexus LoggerManager component contained in the uber jar, and only used System.out if that failed. It would then be possible to register a custom plexus component to add that capability. I've filed such a request in JIRA [MNG-3463]. Perhaps it will make it into 2.1. Robert Egan Wayne Fay [EMAIL PROTECTED] wrote on 03/13/2008 03:13:01 PM: Edit mvn.bat and redirect output somewhere using normal batch file/shell script programming. I don't know how you would accomplish this with Maven plugins and doubt it is even possible with 2.0.x. Wayne On 3/13/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: One of the features of the Ant build I inherited is the ability to auto-magically generate date/time stamped log files of the console output. I'd like to be able to do something like that with the Maven build, but I haven't been able to find any relevant documentation. Can anyone point me in the right direction? This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Logging
One of the features of the Ant build I inherited is the ability to auto-magically generate date/time stamped log files of the console output. I'd like to be able to do something like that with the Maven build, but I haven't been able to find any relevant documentation. Can anyone point me in the right direction? Thanks Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Multi module questions
I have multi-module project. If I execute a phase from the topmost module (mvn compile or mvn install) the reactor runs it for all the submodules and then the topmost module. But it does not seem to be happening for a non-phase goal (specifically mvn scm:update). My questions are 1) Is this the correct behavior or am I doing something wrong and 2) If I want to propogate scm:update to my submodules, how would I do it? Thanks Robert Egan -- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: override a goal within a phase
jar is the default value, so simply deleting the element is insufficient. You must actually change the value to something else, like pom. Robert Egan Paolo Casarini [EMAIL PROTECTED] wrote on 03/06/2008 10:54:15 AM: I don't know... erasing packagingjar/packaging don't change any behaviour. The jar:jar goal is still invoked. Paolo. Il giorno 06/mar/08, alle ore 16:42, Ian Hummel ha scritto: Does that mean you will have to manually bind all the other goals to their respective phases? On Mar 6, 2008, at 7:37 AM, Stephen Connolly wrote: don't use packagingjar/packaging and that will disable the jar:jar On Thu, Mar 6, 2008 at 12:10 PM, Paolo Casarini [EMAIL PROTECTED] wrote: Hi, does anybody can tell me how can I replace the standard jar:jar, in the package phase, with my :jar goal implemented by my Mojo? or is there a way to disable the execution of the standard jar:jar goal? --- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
scm reference works?
I have written my own scm provider for the scm plugin and I am now trying to use it. Unfortunately, the scm provider plugin seems to be very exacting in what it expects for configuration parameters (i.e. their content, not what type of data they are). Normally, I would google SCM Tutorial and not bother the list. But unfortunately, SCM is also an acronym for Supply Chain Management, a very hot topic in google these days it would seem, since it produces almost 400K hits, almost none of which relate to Source Control Management. So, thanks in advance for any links to scm manuals/tutorials. Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: scm reference works?
In order to clarify things, here's some examples of the issues I've faced and am facing. The first one was the use of scm:update instead of scm:checkout. The source control product I use has no concept of update. You simply checkout your files, optionally locking them. If they already exist and are out of date, they are updated. If they do not exist they are checked out. So you can image my dismay when the first thing the scm:checkout operation did was delete my existing source tree! It turns out the scm differentiates between checkout and update, and that really isn't documented anywhere that I can see. It just seems to be assumed by those used to scm. Next up is the scmVersionType tag. If I omit it, the framework tells me it is required. If It is not tag, branch, or revision the framework tells me it is the wrong type. But if I specify one of those, it does not like my scmVersion tag, giving me a message that it is expecting a java.lang.String but got an org.apache.maven.scm.scmTag, scmBranch or scmRevision. Again, I'm sure the required syntax is obvious to developers who use scm, because they are so used to it they don't give it a second thought. Just like they would know the difference between checkout and update. But quite frankly, it's got me stumped, so ANY documentation in this are would be greatly appreciated. It took me a long time to stumble onto the difference between checkout and update, and I'd like to shorten it this time around. Thanks again, Robert Egan Previously, I wrote on 03/05/2008 09:59:24 AM: I have written my own scm provider for the scm plugin and I am now trying to use it. Unfortunately, the scm provider plugin seems to be very exacting in what it expects for configuration parameters (i.e. their content, not what type of data they are). Normally, I would google SCM Tutorial and not bother the list. But unfortunately, SCM is also an acronym for Supply Chain Management, a very hot topic in google these days it would seem, since it produces almost 400K hits, almost none of which relate to Source Control Management. So, thanks in advance for any links to scm manuals/tutorials. Robert Egan -- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
maven-jar-plugin question
The following POM works as expected when run by itself (it uses
org.apache.maven.plugins:maven-jar-plugin:2.1:jar) but when run as part of
a multi-module build it uses
org.apache.maven.plugins:maven-jar-plugin:2.2:jar. Does anyone have any
suggestions as to why this happens and how I can resolve it?
The reason this is an issue is that it needs to construct an empty jar,
which was disallowed in 2.2.
Thanks
Robert Egan
PS: I'm not allowed to put an empty file in the jar, as has previously
been suggested. The reasons are political, not programmatic, and quite out
of my control.
project
descriptionwcmDownstreamInterfaceSSOAuthentication
WebArchive/description
namewcmDownstreamInterfaceSSOAuthentication-swar/name
modelVersion4.0.0/modelVersion
groupIdcom.xxx.integration/groupId
artifactIdwcmDownstreamInterfaceSSOAuthentication-swar/artifactId
parent
groupIdcom.xxx.buildtools/groupId
artifactIdswar/artifactId
version7.5.0.0/version
/parent
properties
dist.folder${root.dir}/framework/dist/dist.folder
/properties
build
finalNamewcmDownstreamInterfaceSSOAuthentication/finalName
plugins
plugin
groupIdcom.xxx.buildtools.plugins/groupId
artifactIdmanifest-plugin/artifactId
configuration
classpath
path${manifest.plugin.classpath}/path
pathframework.jar/path
pathsecurityUtil.jar/path
pathwcmArtifactManager.jar/path
pathwcmCache.jar/path
pathwcmDownstreamInterface.jar/path
pathwcmUserMapping.jar/path
path${library.ejb.artifact}/path
path${library.ejb.framework}/path
path${library.ejb.usermapping}/path
/classpath
/configuration
/plugin
plugin
artifactIdmaven-jar-plugin/artifactId
version2.1/version
/plugin
plugin
artifactIdmaven-dependency-plugin/artifactId
/plugin
/plugins
/build
/project
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error
has misdirected this email, please notify the sender immediately and
destroy this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions
expressed in this email are those of the author personally.
Re: maven-jar-plugin question
Wendy Smoak [EMAIL PROTECTED] wrote on 03/01/2008 09:54:25 PM: On Sat, Mar 1, 2008 at 7:50 PM, [EMAIL PROTECTED] wrote: The following POM works as expected when run by itself (it uses org.apache.maven.plugins:maven-jar-plugin:2.1:jar) but when run as part of a multi-module build it uses org.apache.maven.plugins:maven-jar-plugin:2.2:jar. Does anyone have any suggestions as to why this happens and how I can resolve it? Try putting the maven-jar-plugin declaration in the parent pom, probably in pluginManagement. I could be wrong, but I don't think you can use different versions of the same plugin in the same build. I suspect you're right, and it would make sense to cahce them. However, I can't use 2.1 exclusively either. So I'll probably bind something to add an empty file to the generate-resources phase, and another one to remove it in the verify phase. Thanks for the rapid response, especially on a Saturday night! Robert Egan -- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
exec-maven-plugin exec:java question
What is the difference between arguments and commandLineArgs? I would guess, based on the descriptions, that the former affect the class while the latter affect the JVM, the command line being java. Yet elsewhere in the documentation it says that this runs within the same JVM and you must use exec:exec to change VM parameters, so that would seem to not be the case. Hence, my confusion. Thanks, Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
discuss: module paths
Every example I've seen for multi-module projects uses relative paths.
What are some of the drawbacks that would make absolute paths a poor
design choice, as in the following example?
!-- In the parent pom --
properties
root.dirC:/project/root.dir
/properties
!-- In the various child poms --
modules
module${root.dir}/module1/sub-module1/artifact1a/module
module${root.dir}/module1/sub-module1/artifact1b/module
/modules
Thanks
Robert Egan
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error
has misdirected this email, please notify the sender immediately and
destroy this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions
expressed in this email are those of the author personally.
Re: Resource collections and -X mode
Ah, the dangers of cut and paste programming. :( I wish the Maven reactor had been nice enough to state that Element include does not support the 'name' attribute, instead of just ignoring it. Anyway, chalk this one up to user error, and consider beefing up the -X capabilities of the resource element. Robert Egan [EMAIL PROTECTED] wrote on 01/25/2008 02:59:05 PM: Is there any way for -X to expand my resource elements in resources:resources? They look right, but for some reason they're not working, and the debug information (as shown) is somewhat less than optimal. [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' -- [DEBUG] (f) filters = [] [DEBUG] (f) outputDirectory = [...] [DEBUG] (f) project = [EMAIL PROTECTED] [DEBUG] (f) resources = [EMAIL PROTECTED], [EMAIL PROTECTED] [DEBUG] -- end configuration -- resource directoryframework/apps/wcmSuiteAdministration- ear/modules/wcmSuiteAdministration-war/src/web/directory includes include name=**/*.jsp/ include name=**/*.jsf/ /includes excludes exclude name=**/test// exclude name=WEB-INF// /excludes /resource Directory of framework\apps\wcmSuiteAdministration- ear\modules\wcmSuiteAdministration-war\src\web 12/28/2007 10:52 AMDIR . 12/28/2007 10:52 AMDIR .. 03/17/2006 11:02 AM 905 error.jsp 12/12/2007 08:37 AMDIR jsp 01/24/2008 11:40 AMDIR WEB-INF 1 File(s)905 bytes Directory of framework\apps\wcmSuiteAdministration- ear\modules\wcmSuiteAdministration-war\src\web\jsp 12/12/2007 08:37 AMDIR . 12/12/2007 08:37 AMDIR .. 10/22/2007 07:35 AM 3,662 mainWeb.jsp 1 File(s) 3,662 bytes Directory of framework\apps\wcmSuiteAdministration- ear\modules\wcmSuiteAdministration-war\src\web\WEB-INF 01/24/2008 11:40 AMDIR . 01/24/2008 11:40 AMDIR .. 01/17/2007 10:48 AM11,482 ibm-web-bnd.xmi 06/05/2006 01:32 PM 1,741 ibm-web-ext.xmi 02/27/2007 11:38 PM38,631 web.xml 08/22/2003 05:51 AM 405 weblogic.xml 4 File(s) 52,259 bytes Yet, mainWeb.jsp is just not getting copied. -- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Repeating resource collections
As I continue to move our Ant build to Maven artifacts, I have found myself repeating resource collections, particularly the includes and excludes criteria. In ant, such duplication would be eliminated by defining FileSets and referencing them throughout the build. Is there any equivalent in Maven? Robert Egan -- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Resource collections and -X mode
Is there any way for -X to expand my resource elements in resources:resources? They look right, but for some reason they're not working, and the debug information (as shown) is somewhat less than optimal. [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' -- [DEBUG] (f) filters = [] [DEBUG] (f) outputDirectory = [...] [DEBUG] (f) project = [EMAIL PROTECTED] [DEBUG] (f) resources = [EMAIL PROTECTED], [EMAIL PROTECTED] [DEBUG] -- end configuration -- resource directoryframework/apps/wcmSuiteAdministration-ear/modules/wcmSuiteAdministration-war/src/web/directory includes include name=**/*.jsp/ include name=**/*.jsf/ /includes excludes exclude name=**/test// exclude name=WEB-INF// /excludes /resource Directory of framework\apps\wcmSuiteAdministration-ear\modules\wcmSuiteAdministration-war\src\web 12/28/2007 10:52 AMDIR . 12/28/2007 10:52 AMDIR .. 03/17/2006 11:02 AM 905 error.jsp 12/12/2007 08:37 AMDIR jsp 01/24/2008 11:40 AMDIR WEB-INF 1 File(s)905 bytes Directory of framework\apps\wcmSuiteAdministration-ear\modules\wcmSuiteAdministration-war\src\web\jsp 12/12/2007 08:37 AMDIR . 12/12/2007 08:37 AMDIR .. 10/22/2007 07:35 AM 3,662 mainWeb.jsp 1 File(s) 3,662 bytes Directory of framework\apps\wcmSuiteAdministration-ear\modules\wcmSuiteAdministration-war\src\web\WEB-INF 01/24/2008 11:40 AMDIR . 01/24/2008 11:40 AMDIR .. 01/17/2007 10:48 AM11,482 ibm-web-bnd.xmi 06/05/2006 01:32 PM 1,741 ibm-web-ext.xmi 02/27/2007 11:38 PM38,631 web.xml 08/22/2003 05:51 AM 405 weblogic.xml 4 File(s) 52,259 bytes Yet, mainWeb.jsp is just not getting copied. Thanks Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
MJAR-90 and empty jar files
First, I want to thank everyone who made 2.2 a reality. It's let me cleanup my build quite a bit. Having said that, it seems that you can't please everybody all of the time, especially with a generic tool like the maven-jar-plugin g. I have a business requirement (read: management, not programmatic, decision) to produce a few empty jars in my build. I had hoped the forceCreation configuration option would do the trick, but it doesn't. Since the jars are empty I do not need any 2.2 specific functionality, so I can force 2.1 using pluginversion as a workaround. Is there a cleaner way? Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: MJAR-90 and empty jar files
That would create the jar, but it would not be physically empty, only functionally empty. Robert Egan [EMAIL PROTECTED] wrote on 01/24/2008 07:44:36 AM: Hi, Should work with adding a dummy/empty resource file in src/main/resources. -- Olivier 2008/1/24, [EMAIL PROTECTED] [EMAIL PROTECTED]: First, I want to thank everyone who made 2.2 a reality. It's let me cleanup my build quite a bit. Having said that, it seems that you can't please everybody all of the time, especially with a generic tool like the maven-jar-plugin g. I have a business requirement (read: management, not programmatic, decision) to produce a few empty jars in my build. I had hoped the forceCreation configuration option would do the trick, but it doesn't. Since the jars are empty I do not need any 2.2 specific functionality, so I can force 2.1 using pluginversion as a workaround. Is there a cleaner way? Robert Egan -- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
WAR confusion
I seem to be getting more files than I would like in my WAR. Here is the
configuration (as generated with -X)
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-war-plugin:2.0.2:war' --
[DEBUG] (s) addMavenDescriptor = false
[DEBUG] (f) manifestEntries = {...}
[DEBUG] (f) archive =
[EMAIL PROTECTED]
[DEBUG] (f) archiveClasses = false
[DEBUG] (s) classesDirectory =
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\build\classes
[DEBUG] (f) filters = []
[DEBUG] (f) outputDirectory =
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\build
[DEBUG] (f) primaryArtifact = true
[DEBUG] (s) project = [EMAIL PROTECTED]
[DEBUG] (f) warName = forminstaller
[DEBUG] (s) warSourceDirectory =
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\src\web
[DEBUG] (s) directory = src/web
[DEBUG] (s) includes = [**/*.jsp, **/*.jsf, WEB-INF/]
[DEBUG] (s) excludes = [**/test/, WEB-INF/lib/]
[DEBUG] (f) webResources = [Lorg.apache.maven.model.Resource;@1cfa60a4
[DEBUG] (s) webappDirectory =
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\build\forminstaller
[DEBUG] (f) workDirectory =
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\build\war\work
[DEBUG] -- end configuration --
The warSourceDirectory contains the following two files, which do not seem
to match the includes filter
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\src\web\jsse.jar
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\src\web\upload.jar
but are nonetheless appearing in the generated war, as indicated below...
[INFO] Building war:
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\build\forminstaller.war
[DEBUG] adding directory META-INF/
[DEBUG] adding entry META-INF/MANIFEST.MF
[DEBUG] adding directory WEB-INF/
[DEBUG] adding entry jsse.jar
[DEBUG] adding entry upload.jar
[DEBUG] adding entry upload.jsp
[DEBUG] adding entry WEB-INF/ibm-web-bnd.xmi
[DEBUG] adding entry WEB-INF/ibm-web-ext.xmi
[DEBUG] adding entry WEB-INF/web.xml
For additional insight, here is the relevant pom.xml section
plugin
artifactIdmaven-war-plugin/artifactId
configuration
warSourceDirectorysrc/web/warSourceDirectory
archive
addMavenDescriptorfalse/addMavenDescriptor
manifestEntries/
/archive
webResources
resource
directorysrc/web/directory
includes
include**/*.jsp/include
include**/*.jsf/include
includeWEB-INF//include
/includes
excludes
exclude**/test//exclude
excludeWEB-INF/lib//exclude
/excludes
/resource
/webResources
/configuration
/plugin
Robert Egan
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error
has misdirected this email, please notify the sender immediately and
destroy this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions
expressed in this email are those of the author personally.
Re: WAR confusion
Yes, that was it. Thanks very much.
Robert Egan
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error
has misdirected this email, please notify the sender immediately and
destroy this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions
expressed in this email are those of the author personally.
Wayne Fay [EMAIL PROTECTED]
23-Jan-2008 10:30 AM
Please respond to
Maven Users List users@maven.apache.org
To
Maven Users List users@maven.apache.org
cc
Subject
Re: WAR confusion
I'm not positive, but I would assume the
warSourceDirectorysrc/web/warSourceDirectory
directive is kinda cancelling out the resource/includes excludes you
specify later.
Set that warSourceDirectory to src/null (or create a valid empty
directory) and see what happens.
Wayne
On 1/23/08, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
I seem to be getting more files than I would like in my WAR. Here is the
configuration (as generated with -X)
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-war-plugin:2.0.2:war' --
[DEBUG] (s) addMavenDescriptor = false
[DEBUG] (f) manifestEntries = {...}
[DEBUG] (f) archive =
[EMAIL PROTECTED]
[DEBUG] (f) archiveClasses = false
[DEBUG] (s) classesDirectory =
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\build\classes
[DEBUG] (f) filters = []
[DEBUG] (f) outputDirectory =
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\build
[DEBUG] (f) primaryArtifact = true
[DEBUG] (s) project = [EMAIL PROTECTED]
[DEBUG] (f) warName = forminstaller
[DEBUG] (s) warSourceDirectory =
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\src\web
[DEBUG] (s) directory = src/web
[DEBUG] (s) includes = [**/*.jsp, **/*.jsf, WEB-INF/]
[DEBUG] (s) excludes = [**/test/, WEB-INF/lib/]
[DEBUG] (f) webResources = [Lorg.apache.maven.model.Resource;@1cfa60a4
[DEBUG] (s) webappDirectory =
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\build\forminstaller
[DEBUG] (f) workDirectory =
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\build\war\work
[DEBUG] -- end configuration --
The warSourceDirectory contains the following two files, which do not
seem
to match the includes filter
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\src\web\jsse.jar
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\src\web\upload.jar
but are nonetheless appearing in the generated war, as indicated
below...
[INFO] Building war:
D:\framework\apps\forminstaller-ear\modules\forminstaller-war\build\forminstaller.war
[DEBUG] adding directory META-INF/
[DEBUG] adding entry META-INF/MANIFEST.MF
[DEBUG] adding directory WEB-INF/
[DEBUG] adding entry jsse.jar
[DEBUG] adding entry upload.jar
[DEBUG] adding entry upload.jsp
[DEBUG] adding entry WEB-INF/ibm-web-bnd.xmi
[DEBUG] adding entry WEB-INF/ibm-web-ext.xmi
[DEBUG] adding entry WEB-INF/web.xml
For additional insight, here is the relevant pom.xml section
plugin
artifactIdmaven-war-plugin/artifactId
configuration
warSourceDirectorysrc/web/warSourceDirectory
archive
addMavenDescriptorfalse/addMavenDescriptor
manifestEntries/
/archive
webResources
resource
directorysrc/web/directory
includes
include**/*.jsp/include
include**/*.jsf/include
includeWEB-INF//include
/includes
excludes
exclude**/test//exclude
excludeWEB-INF/lib//exclude
/excludes
/resource
/webResources
/configuration
/plugin
Robert Egan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deploying war to 2 different containers at the same time
Amen to that. I've gotten so frustrated at the lack of basic file support that I've written my own plugin for such elementary goals as file:create file:mkdir file:copy file:move file:append file:delete file:rmdir Robert Egan jimpo [EMAIL PROTECTED] wrote, in part, on 10/30/2007 08:26:03 AM: rantSeems like I am spending days finding out how to do simple things like copying a file, things that I could have done in a few minutes using ant /rant This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: exec-maven-plugin
Tim Kettler [EMAIL PROTECTED] wrote on 10/05/2007 02:02:51 AM: Hi, have a look here [1] for the execution code of the plugin. If the executable returns with an error return code or fails for another reason the plugin fails the build and logs this on the console. As neither of this log statements is in your log output, the shell script you invoke most probably just doesn't return a proper error return code. -Tim [1] https://svn.codehaus.org/mojo/tags/exec-maven-plugin-1.1- beta-1/src/main/java/org/codehaus/mojo/exec/ExecMojo.java I sort of expected this. I had to generate the .bat file myself because there was no way that I could see to call the exec plugin in a loop. So I wrote a plugin to perform the iteration and generate a single .bat with multiple calls to the real .bat. It looks like I'll have to enhance my plugin to include some kind of EXIT command in the single bat. Thanks again Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: Build plugin without using it
Tim Kettler [EMAIL PROTECTED] wrote on 10/05/2007 01:41:33 AM: buildplugins is for actually attaching plugins to the build lifecycle. If you just want to define common configuration (version, executions, ...) for a plugin use pluginManagement. Thanks! That puts a new spin on things and simplifies my life quite a bit. Why isn't this essential tidbit mentioned on any of the plugin how-to pages, or did I just miss it? Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Build plugin without using it
How does one go about calling mvn install for packaging type maven-plugin without actually executing the plugin? I only want to install it. I want others to actually use it. This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: Build plugin without using it
I figured it out. I included a build/build section in one of my parent
poms as a way of setting the different properties controlling the build of
the plugins.
project
...
build
directory${buildtools.custom.dir}/build/${project.name}/directory
sourceDirectory${buildtools.plugin.dir}/${project.name}/sourceDirectory
outputDirectory${buildtools.custom.dir}/build/${project.name}/outputDirectory
/build
...
/project
Replacing that section with these three properties fixed it for all of my
plugins
properties
build.directory${buildtools.custom.dir}/build/${project.name}/build.directory
build.sourceDirectory${buildtools.plugin.dir}/${project.name}/build.sourceDirectory
build.outputDirectory${buildtools.custom.dir}/build/${project.name}/build.outputDirectory
/properties
Is this expected behavior or have I stumbled across a previously untried
combination of elements?
Thanks
Robert Egan
Wendy Smoak [EMAIL PROTECTED] wrote on 10/04/2007 02:59:29 PM:
On 10/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
How does one go about calling mvn install for packaging type
maven-plugin
without actually executing the plugin?
Just 'mvn install' should work... I'm curious what makes you think
otherwise?
--
Wendy
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error
has misdirected this email, please notify the sender immediately and
destroy this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions
expressed in this email are those of the author personally.
Re: Build plugin without using it
Apologies. I was incorrect. The real issue is that I have a parent POM that contains this plugin (and the others), and even though the packaging of that parent is pom, it still seems to want to invoke the execute methods of its contained plugins. This, of course is another issue, specifically how does one have an abstract parent pom. I gather, based on a Nabble search, that it involves profiles in some manner. So I'll just wait on it for now. Thanks again for the help Robert Egan Wendy Smoak [EMAIL PROTECTED] wrote on 10/04/2007 02:59:29 PM: On 10/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: How does one go about calling mvn install for packaging type maven-plugin without actually executing the plugin? Just 'mvn install' should work... I'm curious what makes you think otherwise? This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
exec-maven-plugin
I am using the exec-maven-plugin to manipulate some classes and the exec
fails.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
executions
execution
phaseprocess-classes/phase
goals
goalexec/goal
/goals
configuration
executable${ejbdeploy.output}/executable
/configuration
/execution
/executions
/plugin
${ejbdeploy.output} [if this wraps it's all one line]
D:/profiles/AppSrv01/bin/ejbdeploy.bat
D:/wcmsuite73_maven/framework/components/framework-ejb/../../dist/generic/framework_Account.jar
D:/wcmsuite73_maven/framework/components/framework-ejb/build/
D:/wcmsuite73_maven/framework/components/framework-ejb/../../dist/was6/framework_Account.jar
-cp
D:/wcmsuite73_maven/framework/components/framework-ejb/../../dist/framework.jar
-debug -trace -nowarn -noinform -quiet
Unfortunately, according to the output, the build succeeds. How can I make
the build fail in this scenario?
[INFO] [exec:exec {execution: default}]
[INFO]
[INFO]
D:\wcmsuite73_maven\framework\components\framework-ejbD:/profiles/AppSr
v01/bin/ejbdeploy.bat
D:/wcmsuite73_maven/framework/components/framework-ejb/.
./../dist/generic/framework_Account.jar
D:/wcmsuite73_maven/framework/componen
ts/framework-ejb/build/
D:/wcmsuite73_maven/framework/components/framework-ejb
/../../dist/was6/framework_Account.jar -cp
D:/wcmsuite73_maven/framework/compo
nents/framework-ejb/../../dist/framework.jar -debug -trace -nowarn
-noinform -q
uiet
[INFO] [*Error] ejbModule/META-INF/ejb-jar.xml(Enterprise bean: Account):
CHKJ28
02E: ejb-class class com.ph.framework.entitlements.ejb.impl.AccountBean,
or on
e of its supertypes, cannot be reflected. Check the classpath.
[INFO]
[INFO] Execution Halted: Validation Errors Reported
[INFO] 1 Errors
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing
D:\wcmsuite73_maven\framework\components\framework-ejb\pom.xml
to C:\Documents and
Settings\eganr\.m2\repository\com\ph\framework\framework-ej
b\7.4.0.0\framework-ejb-7.4.0.0.pom
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 43 seconds
[INFO] Finished at: Thu Oct 04 21:03:09 EDT 2007
[INFO] Final Memory: 9M/26M
[INFO]
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error
has misdirected this email, please notify the sender immediately and
destroy this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions
expressed in this email are those of the author personally.
Unusual error from JavaMojoDescriptorExtractor
Greetings, I made a transpositional error in the execute method of my Mojo, and produced some rather unusual diagnostics. Since the root cause was user error there may not be any great interest in looking further, but I'll post it here anyway... getLog().info(Files to be deleted: + files.length); // correct line getLog().info(Files to be deleted : files.length); // Oops! com.thoughtworks.qdox.parser.ParseException: syntax error @[64,1] in ExcludesP lugin.java at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:638) at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java(Compiled Code)) at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:619) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:300) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:316) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312) at com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:369) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52) at com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:366) at org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:544) at org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:84) at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:135) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: Unusual error from JavaMojoDescriptorExtractor
Double oops. Apparently I've left my good typing hands at home :). The real error was here for (int i = 0; i files.length; i++)// Forget the brace resulting in a missing right hand brace at the end of the file. Sorry about that. Robert Egan [EMAIL PROTECTED] wrote on 10/01/2007 10:15:00 AM: Greetings, I made a transpositional error in the execute method of my Mojo, and produced some rather unusual diagnostics. Since the root cause was user error there may not be any great interest in looking further, but I'll post it here anyway... getLog().info(Files to be deleted: + files.length); // correct line getLog().info(Files to be deleted : files.length); // Oops! com.thoughtworks.qdox.parser.ParseException: syntax error @[64,1] in ExcludesP lugin.java at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:638) at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java(Compiled Code)) at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:619) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:300) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:316) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312) at com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:369) at com.thoughtworks.qdox.directorywalker.DirectoryScanner. walk(DirectoryScanner.java:43) at com.thoughtworks.qdox.directorywalker.DirectoryScanner. walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner. scan(DirectoryScanner.java:52) at com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:366) at org.apache.maven.tools.plugin.extractor.java. JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:544) at org.apache.maven.tools.plugin.scanner.DefaultMojoScanner. populatePluginDescriptor(DefaultMojoScanner.java:84) at org.apache.maven.plugin.plugin.AbstractGeneratorMojo. execute(AbstractGeneratorMojo.java:135) at org.apache.maven.plugin.DefaultPluginManager. executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor. executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor. executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor. executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor. executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor. executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor. execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl. invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Some basic questions about the Starteam provider
I've been looking at the maven documentation and the source code for the starteam provider and have some quick questions. 1) StarteamAddCommand, StarteamRemoveCommand do not have a corresponding scm goal. I assume that they provide a kind of internal support for the SCM framework? 2) StarteamEditCommand, StarteamUneditCommand are implemented although the Matrix says they are not. Is the Matrix out of date, or is there some other reason for listing them as not implemented? 3) Does a provider ihave/i to use a command line framework, or was that just done for ease of implementation? Thanks Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
starteam provider
Greetings, Where is the scm source code located, and the code for the StarTeam provider? I was browsing the JIRA issues and thought I might tackle some, although I don't want to promise anything. I am thinking, in particular, of a design flaw in their checkout by label code that forced us to extend the ant task because it caused unacceptable performance in our environment. I would like to verify that the SCM StarTeam provider has propogated that flaw (seems likely, since Ant never bothered to correct it) and perhaps submit our override as an enhancement, since I am certainly going to implement it myself anyway. Regards, Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: starteam provider
Never mind, I found it. I wrote on 09/26/2007 08:22:26 AM: Greetings, Where is the scm source code located, and the code for the StarTeam provider? I was browsing the JIRA issues and thought I might tackle some, although I don't want to promise anything. I am thinking, in particular, of a design flaw in their checkout by label code that forced us to extend the ant task because it caused unacceptable performance in our environment. I would like to verify that the SCM StarTeam provider has propogated that flaw (seems likely, since Ant never bothered to correct it) and perhaps submit our override as an enhancement, since I am certainly going to implement it myself anyway. Regards, Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
maven-scm-provider-starteam
It is not entirely clear from the site documentation how you checkout by label (although the scmVersion and scmVersionType look like good candidates), or is this an area still requiring development? If so, I will create a request in JIRA and even begin working on it. Thanks Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
patching maven-jar-plugin
(Method.java:391) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Sep 24 20:02:55 EDT 2007 [INFO] Final Memory: 4M/9M [INFO] Modified POM (I added a comment to highlight the change) 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; parent artifactIdmaven-plugins/artifactId groupIdorg.apache.maven.plugins/groupId version3/version /parent modelVersion4.0.0/modelVersion artifactIdmaven-jar-plugin/artifactId packagingmaven-plugin/packaging nameMaven Jar Plugin/name version2.1-buildtools/version!-- I changed this -- prerequisites maven2.0/maven /prerequisites dependencies dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-archiver/artifactId version2.2/version /dependency dependency groupIdcommons-lang/groupId artifactIdcommons-lang/artifactId version2.1/version /dependency dependency groupIdorg.apache.maven.shared/groupId artifactIdmaven-plugin-testing-harness/artifactId version1.0-beta-1/version scopetest/scope /dependency /dependencies /project Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: Excluding files from a jar
Known issue. check out these links.
http://www.nabble.com/forum/Search.jtp?forum=178local=yquery=MJAR-30
(previous discussion)
http://jira.codehaus.org/browse/MJAR-30 (patch)
Mark Eramo [EMAIL PROTECTED] wrote on 09/21/2007 01:44:57 PM:
I have been trying to exclude certain files from the jar however it does
not seem to be working. I am trying to do this with the include and
exclude switches. I searched the mailing list and some posts say this
should work, others say no so I am trying to find out if anyone has
accomplished this with Maven 2.0.
For example, I have this in my pom.xml:
resources
resource
directory${basedir}/target/directory
excludes
exclude**/web/handlers/**/*.*/exclude
/excludes
/resource
resource
directory${basedir}/directory
includes
includeReleaseNotes.txt/include
/includes
/resource
/resources
Now the include works, it adds the release notes to the jar but the
exclude does not work. Very strange. Any ideas or comments on how to
accomplish this would be much appreciated.
I know I could do it with the ant plugin after the compile phase (move
the code I do not want out of the target folder) but I was hoping I
could simply accomplish this with the excludes switch.
Regards,
Mark
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error
has misdirected this email, please notify the sender immediately and
destroy this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions
expressed in this email are those of the author personally.
Re: Excluding files from a jar
Here's a technique I received just the other day. I haven't done it yet, because the Maven port has been moved down my priority list by senior management, but it should work Here's how I patch Maven jars: download the code from svn apply patch modify pom to add -mycompany to version number ie 2.2.1.0-mycompany (use your own company name here) mvn install the file into your repo lock down the plugin in your poms to the new version version[2.2.1-mycompany]/version Its generally a bad idea to specify a version that might actually be used in the future by the real maintainers of the plugin, that's why -mycompany is a good idea. You definitely don't want to just bump the version by 1. Mark Eramo [EMAIL PROTECTED] wrote on 09/21/2007 02:07:26 PM: Thanks for the links Robert. Based on the 2nd link, it looks like there is some sort of patch for the plugin. Is this something that I can install locally and if so, can you recommend the best way to do this? This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
patching maven-jar-plugin
I'd like to implement a patch for maven-jar-plugin locally. How is that done? I have created a local repository (file:// etc) for our custom plugins and some parent poms shared by multiple artifacts. Should I deploy my plugin there? Will it be preferred over the remote one if I do? The patch is already in jira (MJAR-30) so it's likely to be rolled up eventually, but I'd prefer not to wait. Please note that I do not use any tools, just maven from the command line. Thanks Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: Is there a property for parent directory?
Is this ${parent} property generally available, i.e. ${parent.artifactId},
etc
It would help me refactor a number of places where I use something similar
to this in a parent POM
properties
super.artifactId${artifactId}super.artifactId
/properties
Roland Asmann [EMAIL PROTECTED] wrote on 09/11/2007 06:49:55 AM:
Yes there is: ${parent.basedir} should be the one you need
Be carefull though, if your child-project are deeper than one level, you
should use ${parent.parent.basedir} (and so on).
Isn't it possible for you to make a dependency of some kind to the
tools-project? Or build your tools as maven-plugins, that way you won't
need
the variables!
[snipped discussion of why...]
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error
has misdirected this email, please notify the sender immediately and
destroy this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions
expressed in this email are those of the author personally.
Dependency management
I have a question that I hope isn't too basic. I've been trying to reconcile the behavior of dependency management with my expectations. I'll state in advance that I'm more than willing to admit that my expectations might be unrealistic. We've got a home grown dependency mechanism that works as follows: If artifact A requires artifact B and artifact B does not exist it builds artifact B before building artifact A. To further clarify what I'd like to do, I had originally started with the modules element but quickly ran into this screnario: artifacts A and B are built in the same POM (packagingpom/packaging), and both require artifact C. This does not make it past the reactor engine, which will not allow artifact C to appear more than once. Is this behavior possible with the dependencyManagement tags? So far it doesn't seem likely, but perhaps I'm not understanding dependency management, which brings us back to that start of this message. Thanks Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: Dependency management
Eric Redmond [EMAIL PROTECTED] wrote on 08/21/2007 12:12:55 PM: On 8/21/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I have a question that I hope isn't too basic. I've been trying to reconcile the behavior of dependency management with my expectations. I'll state in advance that I'm more than willing to admit that my expectations might be unrealistic. We've got a home grown dependency mechanism that works as follows: If artifact A requires artifact B and artifact B does not exist it builds artifact B before building artifact A. That isn't really a dependency mechanism in Maven - that is a module hierarchy. As long as module B exists in the set of modules along with A, and A depends on B, then B will be built first. Essentially, yes. If the reactor allowed it I would use module hierarchies. To further clarify what I'd like to do, I had originally started with the modules element but quickly ran into this screnario: artifacts A and B are built in the same POM (packagingpom/packaging), and both require artifact C. This does not make it past the reactor engine, which will not allow artifact C to appear more than once. True - why would you want the same artifact built more than once? You wouldn't. Our home grown system remembers that you've already visited the module during this phase and skips it for visits 2 through N. Is this behavior possible with the dependencyManagement tags? So far it doesn't seem likely, but perhaps I'm not understanding dependency management, which brings us back to that start of this message. I'm not understanding what you want to do. Is what behavior possible? Making the reactor build a project twice? If that is your question, then no. Thanks for the explanation. I didn't think dependency management was the answer either. I'll have to port our home grown system to a plugin at some point, or convince management to re-engineer the build process. Thanks again, Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: Dependency management
I'd like to thank you again for taking time to work with me on this. I have been asked to address a production problem for now but I will attempt to post a concrete example from home this evening or no later than tomorrow morning (my TZ is GMT +5). Robert Egan Tim Kettler [EMAIL PROTECTED] wrote on 08/21/2007 01:03:05 PM: Can you give a somewhat more specific example what the reactor does not allow? The scenario you describe above is a fairly standard use-case I would say. Perhaps a set of minimal example poms and a short description of what you expect them to do would be helpful. Maven calculates the dependency tree for the set of reactor projects and then orders the builds of the projects (modules) in such an order that all dependencies of a module are available when the module is build. So what you want to do should be entirely possible with maven out of the box... Or I totally misunderstand what you want to do. Eric Redmond [EMAIL PROTECTED] wrote on 08/21/2007 01:17:35 PM: Again, I am confused. What use-case do you have where you cannot just create a multi-module project that contains project A and B as modules? This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: Dependency management
As promised: I wrote on 08/21/2007 03:13:21 PM: I'd like to thank you again for taking time to work with me on this. I have been asked to address a production problem for now but I will attempt to post a concrete example from home this evening or no later than tomorrow morning (my TZ is GMT +5). Consider the following directory structure /base /artifact1 /artifact2 /artifact3 /artifact3a The relevant sections of /base/pom.xml look like this: packagingpom/packaging modules moduleartifact1/module moduleartifact2/module moduleartifact3/module /modules /base/artifact1/pom.xml and /base/artifact2/pom.xml are simple jars, so you can call mvn clean install from either folder. The relevant sections of /base/artifact3/pom.xml look like this: packagingpom/packaging modules module../artifact1/module module../artifact2/module moduleartifact3a/module /modules While you can do mvn clean install from /base/artifact3/ you will not be allowed to do it from /base, because the reactor won't let you visit artifact1 and artifact2 twice. This is a very simplified example. Our build contains several dozen artifacts with numerous dependencies similar to the above. Also, I am willing to live with the fact that this may not be the best design and that it may be easier to re-engineer the build, if that is your recommendation. Thanks again Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: Dependency management
Wayne Fay [EMAIL PROTECTED] wrote on 08/21/2007 08:52:31 PM: I think what you really want is simply a dependency on artifact1 and artifact2 in your artifact3 pom, not module../artifact1/module. I'm a little surprised that ../ notation is even allowed in the module node, to be honest. Then, when you build from the top, all of your projects will be built in the proper order assuming your dependencies are declared properly, and all modules will use the most recent bits of code in each module as the various artifacts are produced. If you build from a3, Maven will use the most recently built (and installed into your local repo) files from a1 and a2. It will not go into a1 and a2 to rebuild those files, however. Wayne I have also come to this conclusion. It is the correct approach to dependency management, although I am concerned that the developers will consider it a loss of functionality because they have become used to the home grown system, which pretty much lets you build any part of the product at any time. Perhaps I'll offer to write a plugin as part of phase 2 of the rollout. On 8/21/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Consider the following directory structure /base /artifact1 /artifact2 /artifact3 /artifact3a The relevant sections of /base/pom.xml look like this: packagingpom/packaging modules moduleartifact1/module moduleartifact2/module moduleartifact3/module /modules /base/artifact1/pom.xml and /base/artifact2/pom.xml are simple jars, so you can call mvn clean install from either folder. The relevant sections of /base/artifact3/pom.xml look like this: packagingpom/packaging modules module../artifact1/module module../artifact2/module moduleartifact3a/module /modules While you can do mvn clean install from /base/artifact3/ you will not be allowed to do it from /base, because the reactor won't let you visit artifact1 and artifact2 twice. This is a very simplified example. Our build contains several dozen artifacts with numerous dependencies similar to the above. Also, I am willing to live with the fact that this may not be the best design and that it may be easier to re-engineer the build, if that is your recommendation. Thanks again Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
manifest classpath
I've looked through the examples for this and it seems simple enough. However, I'd really like to have my classpath as a series of path elements for the sake of legibility and future maintnance, i.e. classpath entrypath1/entry entrypath2/entry entrypath3/entry /classpath instead of manifest classpathpath1 path2 path3/classpath /manifest It may not seem like much in the simple example given here, but here's a class path from one of our production jars: Class-Path: plugins/framework plugins/checkservices plugins/transferse rvices plugins/alerts plugins/pr plugins/pr/achapps plugins/pr/wireap ps wcmPrincipals-hotfix.jar wcmPrincipals.jar securityUtil-hotfix.jar securityUtil.jar wcmCache-hotfix.jar wcmCache.jar lib/apache/jakart a-commons/commons-cli-1.0.jar lib/apache/jakarta-commons/commons-coll ections-3.1.jar lib/apache/jakarta-commons/commons-dbcp-1.2.1.jar lib /apache/jakarta-commons/commons-lang-2.1.jar lib/apache/jakarta-commo ns/commons-pool-1.2.jar lib/apache/jakarta-commons/commons-logging-1. 0.4/commons-logging.jar lib/apache/JCS/jcs-1.2.6.8.jar lib/oswego.edu /util-concurrent-1.3.4.jar lib/jradius/jradius.jar lib/jradius/jradiu s-dictionary.jar lib/gnu/gnu-crypto.jar lib/httpclient/commons-codec- 1.3.jar lib/httpclient/commons-httpclient-3.0.jar lib/emory.edu/backp ort-util-concurrent-2.2/backport-util-concurrent.jar lib/oracle/jdbc- 10.2.0.1.0/ojdbc14.jar lib/oracle/jdbc-10.2.0.1.0/jdbc_rowset_tiger1. 0.1mrel-ri/rowset.jar lib/jdom/jdom-1.0/jdom.jar lib/rsa/authapi.jar lib/apache/log4j/log4j-1.2.8.jar So I'm sure you can see why I'd like the former approach. Any ideas would be welcome. Thanks Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Date and time processing
Does Maven or one of it's plugins support date/time stamping? In
particular, I'd like to add the build date to my Manifests with something
like
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
archive
manifestEntries
...
Build-Time${now}/Build-Time
...
/manifestEntries
/archive
/configuration
/plugin
Thanks
Robert Egan
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error
has misdirected this email, please notify the sender immediately and
destroy this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions
expressed in this email are those of the author personally.
Re: manifest classpath
The former, and thanks for the link. I'll bring the issue there (if it hasn't been raised already). Robert Egan Wayne Fay [EMAIL PROTECTED] 16-Aug-2007 11:27 AM Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject Re: manifest classpath Are you asking about a Maven2 pom configuration entry, or the actual Class-Path line in your MANIFEST.MF file generated by Maven? If you're asking about Maven, please file a RFE in JIRA and someone will take a look at your issue. I'd suggest filing under MJAR: http://jira.codehaus.org/browse/MJAR If you're asking about the MANIFEST.MF file itself, you are welcome to take this up with Sun and/or the JCP. Until then, the Jar specification requires that we continue to use the current formatting of the classpath: http://java.sun.com/javase/6/docs/technotes/guides/jar/jar.html Wayne On 8/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I've looked through the examples for this and it seems simple enough. However, I'd really like to have my classpath as a series of path elements for the sake of legibility and future maintnance, i.e. classpath entrypath1/entry entrypath2/entry entrypath3/entry /classpath instead of manifest classpathpath1 path2 path3/classpath /manifest It may not seem like much in the simple example given here, but here's a class path from one of our production jars: Class-Path: plugins/framework plugins/checkservices plugins/transferse rvices plugins/alerts plugins/pr plugins/pr/achapps plugins/pr/wireap ps wcmPrincipals-hotfix.jar wcmPrincipals.jar securityUtil-hotfix.jar securityUtil.jar wcmCache-hotfix.jar wcmCache.jar lib/apache/jakart a-commons/commons-cli-1.0.jar lib/apache/jakarta-commons/commons-coll ections-3.1.jar lib/apache/jakarta-commons/commons-dbcp-1.2.1.jar lib /apache/jakarta-commons/commons-lang-2.1.jar lib/apache/jakarta-commo ns/commons-pool-1.2.jar lib/apache/jakarta-commons/commons-logging-1. 0.4/commons-logging.jar lib/apache/JCS/jcs-1.2.6.8.jar lib/oswego.edu /util-concurrent-1.3.4.jar lib/jradius/jradius.jar lib/jradius/jradiu s-dictionary.jar lib/gnu/gnu-crypto.jar lib/httpclient/commons-codec- 1.3.jar lib/httpclient/commons-httpclient-3.0.jar lib/emory.edu/backp ort-util-concurrent-2.2/backport-util-concurrent.jar lib/oracle/jdbc- 10.2.0.1.0/ojdbc14.jar lib/oracle/jdbc-10.2.0.1.0/jdbc_rowset_tiger1. 0.1mrel-ri/rowset.jar lib/jdom/jdom-1.0/jdom.jar lib/rsa/authapi.jar lib/apache/log4j/log4j-1.2.8.jar So I'm sure you can see why I'd like the former approach. Any ideas would be welcome. Thanks Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-antrun-plugin
Do the if and/or unless attributes of the tasks element actually work?
It seems that my ant code gets run no matter what.
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phaseinstall/phase
configuration
tasks if=${XX} !-- runs even if i change to unless
--
echoEcho here/echo
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
Robert Egan
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error
has misdirected this email, please notify the sender immediately and
destroy this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions
expressed in this email are those of the author personally.
Maven Wagon
Is there additional information on Wagon besides http://maven.apache.org/wagon ? This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Maven plugin for WebSphere 6.x
I have spent the last few hours looking the Maven 2 equivalent of the following 1.1 plugin http://maven-plugins.sourceforge.net/maven-was5-plugin/index.html without success. There doesn't seem to be anything at the mojo website either. Have I overlooked it, or has IBM decided not to participate in Open Source any more? Thanks Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Large number of dependencies
I've just begun implementing maven into our build process. I have some artifacts with a large number of dependencies. ibm\websphere\j2ee\6.0.2\j2ee-6.0.2.jar ibm\websphere\runtime\6.0.2\runtime-6.0.2.jar ibm\websphere\rsadaptercci\6.0.2\rsadaptercci-6.0.2.jar ibm\websphere\rsadapterspi\6.0.2\rsadapterspi-6.0.2.jar ibm\websphere\rsaexternal\6.0.2\rsaexternal-6.0.2.jar ibm\websphere\sas\6.0.2\sas-6.0.2.jar ibm\websphere\ras\6.0.2\ras-6.0.2.jar ibm\websphere\bootstrap\6.0.2\bootstrap-6.0.2.jar ibm\websphere\emf\6.0.2\emf-6.0.2.jar ibm\websphere\iwsorb6.0.2\iwsorb-6.0.2.jar ibm\websphere\utils6.0.2\utils-6.0.2.jar ibm\websphere\wssec\6.0.2\wssec-6.0.2.jar ibm\websphere\admin\6.0.2\admin-6.0.2.jar ibm\websphere\management\6.0.2\management-6.0.2.jar ibm\websphere\wasjmx\6.0.2\wasjmx-6.0.2.jar ibm\websphere\wsexception\6.0.2\wsexception-6.0.2.jar ibm\websphere\jsf-api\6.0.2\jsf-api-6.0.2.jar ibm\websphere\ws-jsf\6.0.2\ws-jsf-6.0.2.jar ibm\websphere\webservices\6.0.2\webservices-6.0.2.jar I'd like to bundle them into a sort of dependency group that would then take only one entry in my POMs. Suggestions? This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: Large number of dependencies
It did not work, but pehaps I'm doing something wrong, because it still wants a jar. I added an appropriately named empty jar (manifest only) and even tried putting the pom in the jar. For now, I must put it on the back burner and deal with production issues (this counts as RD). Thanks anyway for taking the time to answer. Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally. Wayne Fay [EMAIL PROTECTED] wrote on 07/20/2007 10:09:01 AM: Yes, that works. Create a pom with no code, packaging pom, and then depend on that pom in your real code project. It should bring all the dependencies along with it. Wayne On 7/20/07, Lalor, Brian [EMAIL PROTECTED] wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 9:20 AM To: users@maven.apache.org Subject: Large number of dependencies I'd like to bundle them into a sort of dependency group that would then take only one entry in my POMs. Suggestions? Dunno if this would work, but could you just create a .pom file in your repository without an associated JAR and declare the dependencies in there? Then you'd declare each project's dependency on that single entity. - 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: Large number of dependencies
Yes, that's done it. I prefer this approach because it brings the handling of third party jars in line with the ones we've created ourselves, instead of being a special case. Thanks again! Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally. Wayne Fay [EMAIL PROTECTED] wrote on 07/20/2007 11:22:11 AM: Brian, that works too. But most of the time, you've got several projects that all need the same collection of jars, so you end up installing this pom by itself and then you can add it to any project at any time. Wayne On 7/20/07, Lalor, Brian [EMAIL PROTECTED] wrote: Wayne gave me more credit than I deserved, but we weren't quite talking about the same thing. Forget putting anything directly into the repository. Instead, assuming you're using a multi-module project, create a new sub-module and define your dependencies there. So, your tree would look something like this: . top-level dir (/; groupId: com.foo, artifactId: top-level) |- pom.xml |- big-ass-dependency (groupId: com.foo, artifactId: big-ass-dependency) | `- pom.xml |- web-proj `- pom.xml In /big-ass-dependency/pom.xml, you'd specify your dependencies. In /web-proj/pom.xml, you'd declare your dependency on big-ass-dependency: dependency groupIdcom.foo/groupId artifactIdbig-ass-dependency/artifactId /dependency I'd like to model this in maven just for my own edification, but I don't have time right now. :-( -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 10:35 AM To: Maven Users List Subject: Re: Large number of dependencies It did not work, but pehaps I'm doing something wrong, because it still wants a jar. I added an appropriately named empty jar (manifest only) and even tried putting the pom in the jar. For now, I must put it on the back burner and deal with production issues (this counts as RD). Thanks anyway for taking the time to answer. Wayne Fay [EMAIL PROTECTED] wrote on 07/20/2007 10:09:01 AM: Yes, that works. Create a pom with no code, packaging pom, and then depend on that pom in your real code project. It should bring all the dependencies along with it. Wayne On 7/20/07, Lalor, Brian [EMAIL PROTECTED] wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 9:20 AM To: users@maven.apache.org Subject: Large number of dependencies I'd like to bundle them into a sort of dependency group that would then take only one entry in my POMs. Suggestions? Dunno if this would work, but could you just create a .pom file in your repository without an associated JAR and declare the dependencies in there? Then you'd declare each project's dependency on that single entity. - 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]
