RE: [Q] Skinny Wars and Taglibs
Thanks, Vincent! I updated my poms to extract the TLDs from the jar files and place them un WEB-INF. This seems to be working for now. However, I did notice that when building the war, it is placing the TLDs in web-inf and not WEB-INF. Not sure if that will make a difference or not? Thanks, Ken -Original Message- From: Vincent Latombe [mailto:vincent.lato...@gmail.com] Sent: Friday, August 31, 2012 10:20 AM To: Maven Users List Subject: Re: [Q] Skinny Wars and Taglibs I think it depends on the container, but you actually need the tlds (at least) in the .war. (under WEB-INF). Vincent 2012/8/30 Hoying, Ken ken_hoy...@premierinc.com I am betting someone already has a clever solution to the following problem. I am trying to create a deployment ear which contains a war. I did not want to bloat the ear by repeating the jar files in both the EAR and WAR libs. So I used the skinnyWars setting for the maven-ear-plugin (v2.7). At first I thought this was going to work great and it almost did. However, my JSP pages are now complaining that they cannot find the taglibs. I am getting the following error: The absolute uri: http://www.springframework.org/tags cannot be resolved in either web.xml or the jar files deployed with this application It seems that the sever really wants these jars to be located under the WAR's lib. Has anyone found a way around this? Thanks in advance! Ken - ***Note:The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying to the message and deleting it from your computer. Thank you. Premier Inc. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - ***Note:The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying to the message and deleting it from your computer. Thank you. Premier Inc.
RE: [Q] v3.0.3 exec-maven-plugin hanging
Thanks, Curtis! I had not thought of that. I was able to work around my issue though by using the maven-antrun-plugin with a java task. It works fine when I run it this way. Thank you! Ken -Original Message- From: ctrueden.w...@gmail.com [mailto:ctrueden.w...@gmail.com] On Behalf Of Curtis Rueden Sent: Wednesday, August 29, 2012 4:08 PM To: Maven Users List Subject: Re: [Q] v3.0.3 exec-maven-plugin hanging Hi Ken, Does anyone have any ideas? Just one: did you try hitting Ctrl+backslash (Ctrl+break on Windows) from the console after it hangs to get a full stack trace? If might be helpful when combined with a little digging in the Maven source code. Regards, -Curtis On Wed, Aug 29, 2012 at 12:59 PM, Hoying, Ken ken_hoy...@premierinc.comwrote: I am hoping someone can assist me with a very strange problem that I am having trouble with. I have project with various modules that is structure, as follows: |--- project |--- pom.xml |--- ear |--- pom.xml |--- services |--- pom.xml |--- web |--- pom.xml The pom file under the web directory uses exec-maven-plugin and the exec goal to run a java program that compiles Dojo for me. When I install on this pom under the web directory, everything works perfectly. However when I install from the pom under the project directory, the java program is executed and appears to finish correctly but maven appears to hang or to still be waiting on it. I do not see any issues when run under debug that would help me. Does anyone have any ideas? I would greatly appreciate any assistance that you could provide. Thank you! - ***Note:The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying to the message and deleting it from your computer. Thank you. Premier Inc. - ***Note:The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying to the message and deleting it from your computer. Thank you. Premier Inc. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[Q] Skinny Wars and Taglibs
I am betting someone already has a clever solution to the following problem. I am trying to create a deployment ear which contains a war. I did not want to bloat the ear by repeating the jar files in both the EAR and WAR libs. So I used the skinnyWars setting for the maven-ear-plugin (v2.7). At first I thought this was going to work great and it almost did. However, my JSP pages are now complaining that they cannot find the taglibs. I am getting the following error: The absolute uri: http://www.springframework.org/tags cannot be resolved in either web.xml or the jar files deployed with this application It seems that the sever really wants these jars to be located under the WAR's lib. Has anyone found a way around this? Thanks in advance! Ken - ***Note:The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying to the message and deleting it from your computer. Thank you. Premier Inc. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[Q] v3.0.3 exec-maven-plugin hanging
I am hoping someone can assist me with a very strange problem that I am having trouble with. I have project with various modules that is structure, as follows: |--- project |--- pom.xml |--- ear |--- pom.xml |--- services |--- pom.xml |--- web |--- pom.xml The pom file under the web directory uses exec-maven-plugin and the exec goal to run a java program that compiles Dojo for me. When I install on this pom under the web directory, everything works perfectly. However when I install from the pom under the project directory, the java program is executed and appears to finish correctly but maven appears to hang or to still be waiting on it. I do not see any issues when run under debug that would help me. Does anyone have any ideas? I would greatly appreciate any assistance that you could provide. Thank you! - ***Note:The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying to the message and deleting it from your computer. Thank you. Premier Inc.
RE: How to get around a Maven Bug?
Thank you! I had to use version 1.7 of the digester, but that did the trick. -Original Message- From: Barrie Treloar [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2008 11:56 PM To: Maven Users List Subject: Re: How to get around a Maven Bug? On Thu, Jun 19, 2008 at 11:46 PM, Hoying, Ken [EMAIL PROTECTED] wrote: I am getting the error below when attempting to add the Apache commons-validator version 1.3.1 to my project. It looks like this might be a known issue in Maven based on this bug report: http://jira.codehaus.org/browse/MNG-2123?page=com.atlassian.jira.plugin. system.issuetabpanels:worklog-tabpanel. I am relatively new to Maven and am not sure how I can work around the issue. Any help would be greatly appreciated! [INFO] Using default encoding to copy filtered resources. Downloading: http://c3qubuild1:8081//commons-validator/commons-validator/1.3.1/comm on s-validator-1.3.1.pom Downloading: http://repo1.maven.org/maven2/commons-validator/commons-validator/1.3. 1/ commons-validator-1.3.1.pom 8K downloaded Downloading: http://c3qubuild1:8081//jcsc/jcsc-gnu-regexp/0.98.1/jcsc-gnu-regexp-0. 98 .1.pom Downloading: http://repo1.maven.org/maven2/jcsc/jcsc-gnu-regexp/0.98.1/jcsc-gnu-reg ex p-0.98.1.pom [INFO] -- -- [ERROR] FATAL ERROR [INFO] -- -- [INFO] version was null for commons-digester:commons-digester Have you tried including as a dependency in your pom commons-digester? commons-validator:1.3 uses the following definition. dependency groupIdcommons-digester/groupId artifactIdcommons-digester/artifactId version1.6/version /dependency - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - ***Note:The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying to the message and deleting it from your computer. Thank you. Premier Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to get around a Maven Bug?
I am getting the error below when attempting to add the Apache commons-validator version 1.3.1 to my project. It looks like this might be a known issue in Maven based on this bug report: http://jira.codehaus.org/browse/MNG-2123?page=com.atlassian.jira.plugin. system.issuetabpanels:worklog-tabpanel. I am relatively new to Maven and am not sure how I can work around the issue. Any help would be greatly appreciated! [INFO] Using default encoding to copy filtered resources. Downloading: http://c3qubuild1:8081//commons-validator/commons-validator/1.3.1/common s-validator-1.3.1.pom Downloading: http://repo1.maven.org/maven2/commons-validator/commons-validator/1.3.1/ commons-validator-1.3.1.pom 8K downloaded Downloading: http://c3qubuild1:8081//jcsc/jcsc-gnu-regexp/0.98.1/jcsc-gnu-regexp-0.98 .1.pom Downloading: http://repo1.maven.org/maven2/jcsc/jcsc-gnu-regexp/0.98.1/jcsc-gnu-regex p-0.98.1.pom [INFO] [ERROR] FATAL ERROR [INFO] [INFO] version was null for commons-digester:commons-digester [INFO] [INFO] Trace java.lang.NullPointerException: version was null for commons-digester:commons-digester at org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact .java:362) at org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225 ) at org.apache.maven.artifact.resolver.ResolutionNode.getDependencyTrail(Res olutionNode.java:118) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(Defa ultArtifactCollector.java:97) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:292) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:280) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependenci es(DefaultPluginManager.java:1246) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:401) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) - ***Note:The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying to the message and deleting it from your computer. Thank you. Premier Inc.
Maven ... Eclipse ... Antrun Plugin
I have a antrun plugin set up in my POM file which does not specify a goal as I want to run it on demand only. When executing from the command line everything works as expected. However, if I attempt to run any goals on the POM from within Eclipse using an External Builder to initiate the command line execution, I get the following error: [INFO] Failed to construct build plan for: com.premierinc:scaEar:ear:1.0-SNAPSHOT ( task-segment: [package] ). Reason: No lifecycle phase binding can be found for goal: run, specified as a part of the execution: defaultin plugin: org.apache.maven.plugins:maven-antrun-plugin This plugin was resolved successfully. However, the mojo metadata it contains does not specify a default lifecycle phase binding. Please provide a valid phase/ specification for execution: default in plugin: org.apache.maven.plugins:maven-antrun-plugin Has anyone seen this before or have a resolution to the issue? I am not sure why this would occur. It seems that Eclipse is juts initiating the same thing that I am from the command line. So why would maven behave differently? Thanks in advance, Ken Hoying - ***Note:The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying to the message and deleting it from your computer. Thank you. Premier Inc.
