Re: Spring context dependency not found..
Hi Mirko, Correct, it's an Eclipse plugin, not a Maven one, I should have been more careful in my naming it. The question I still have though is: should I run any goal, like mvn eclipse:m2eclipse for example, before going to Eclipse and doing a dependency update ? Thanks ! Stephane -- View this message in context: http://maven.40175.n5.nabble.com/Spring-context-dependency-not-found-tp5444070p5453114.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Spring context dependency not found..
Stephane, You should never ever run mvn eclipse:anything-at-all if you're using m2e in Eclipse. They are very different from each other and only interact in bad ways. If you have been doing this then I suggest that you: a) remove associated projects from Eclipse b) delete all .project and .classpath files and the .settings folder from these projects c) import the projects back into eclipse as Existing Maven Projects Cheers, Steve C On 03/02/2012, at 1:16 AM, Stephane-3 wrote: I am using the m2e Maven plugin for Eclipse. And so I guess I cannot run the goal mvn eclipse:eclipse but should run the goal mvn eclipse:m2eclipse As I was running Maven 2.2.1 and m2e requires Maven 2.4 I updated Maven. I could not find any 2.4 version on the download website though. So I downloaded and installed Maven 3.0.4 and got it running. But wen doing the goal eclipse:m2eclipse I get the following error: [ERROR] Could not find goal 'm2eclipse' in plugin org.apache.maven.plugins:maven-eclipse-plugin:2.8 among available goals to-maven, add-maven-repo, myeclipse-clean, configure-workspace, help, rad-clean, install-plugins, eclipse, myeclipse, rad, clean, remove-cache, make-artifacts - [Help 1] org.apache.maven.plugin.MojoNotFoundException: Could not find goal 'm2eclipse' in plugin org.apache.maven.plugins:maven-eclipse-plugin:2.8 among available goals to-maven, add-maven-repo, myeclipse-clean, configure-workspace, help, rad-clean, install-plugins, eclipse, myeclipse, rad, clean, remove-cache, make-artifacts at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:267) at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:235) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:86) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:98) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) -- View this message in context: http://maven.40175.n5.nabble.com/Spring-context-dependency-not-found-tp5444070p5450809.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Question on resources plugin
Jeff,
Filtering of web app resources is handled by the maven-war-plugin.
Have a look at
http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html.
Cheers,
Steve C
On 03/02/2012, at 11:31 AM, Jeff Lowery wrote:
Hello-
I've created a properties file and refer to it in a filter element. The
properties are referenced in a web.xml file via ${} parameters.
By using the following setup, I get a web.xml that has the parameters
replaced:
filters
filterwebApp.properties/filter
/filters
resources
resource
directorysrc/main/webapp/WEB-INF/directory
filteringtrue/filtering
includes
includeweb.xml/include
/includes
/resource
/resources
But the generated web.xml file goes to the target/classes folder, whereas I
want it to go to the target/warfile/WEB-INF folder.
If I add the following:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-resources-plugin/artifactId
configuration
phasepackage/phase
outputDirectorytarget/${project.build.finalName}/WEB-INF/outputDirectory
/configuration
/plugin
It looks like the generated web.xml gets clobbered by the original web.xml in
src.
Someone here just now suggested modifying the war plugin config to pull
web.xml from the target/classes folder instead of src. Sounds workable.
Any other ideas?
-- Jeff
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Versions Maven Plugin 1.3 released
The Mojo team is pleased to announce the release of the Versions Maven Plugin, version 1.3. NOTE: This is the last release line that will support running on Maven 2.0.x. NOTE: This version contains one method that requires JDK 1.5, version 1.3.1 of this plugin will be released tomorrow and that will run on JDK 1.4. Version 2.0 of the plugin will require Maven 2.2.1 and JDK 1.5. NOTE: One major change in this version is that the versions:display-plugin-updates goal has been modified to take into account the project and plugin's prerequisites, so that if you invoke it on a project that specifies a minimum of Maven 2.0.9, it will only suggest plugin updates that are compatible with that version of Maven... oh and it will also suggest what plugin updates are available if you increase the minimum version of Maven in your project's pom. The Versions Plugin has the following goals. * versions:compare-dependencies compares the dependency versions of the current project to the dependency management section of a remote project. * versions:display-dependency-updates scans a project's dependencies and produces a report of those dependencies which have newer versions available. * versions:display-plugin-updates scans a project's plugins and produces a report of those plugins which have newer versions available. * versions:display-property-updates scans a projectand produces a report of those properties which are used to control artifact versions and which properies have newer versions available. * versions:update-parent updates the parent section of a project so that it references the newest available version. For example, if you use a corporate root POM, this goal can be helpful if you need to ensure you are using the latest version of the corporate root POM. * versions:update-properties updates properties defined in a project so that they correspond to the latest available version of specific dependencies. This can be useful if a suite of dependencies must all be locked to one version. * versions:update-child-modules updates the parent section of the child modules of a project so the version matches the version of the current project. For example, if you have an aggregator pom that is also the parent for the projects that it aggregates and the children and parent versions get out of sync, this mojo can help fix the versions of the child modules. (Note you may need to invoke Maven with the -N option in order to run this goal if your project is broken so badly that it cannot build because of the version mis-match). * versions:lock-snapshots searches the pom for all -SNAPSHOT versions and replaces them with the current timestamp version of that -SNAPSHOT, e.g. -20090327.172306-4 * versions:unlock-snapshots searches the pom for all timestamp locked snapshot versions and replaces them with -SNAPSHOT. * versions:resolve-ranges finds dependencies using version ranges and resolves the range to the specific version being used. * versions:set can be used to set the project version from the command line. * versions:use-releases searches the pom for all -SNAPSHOT versions which have been released and replaces them with the corresponding release version. * versions:use-next-releases searches the pom for all non-SNAPSHOT versions which have been a newer release and replaces them with the next release version. * versions:use-latest-releases searches the pom for all non-SNAPSHOT versions which have been a newer release and replaces them with the latest release version. * versions:use-next-snapshots searches the pom for all non-SNAPSHOT versions which have been a newer -SNAPSHOT version and replaces them with the next -SNAPSHOT version. * versions:use-latest-snapshots searches the pom for all non-SNAPSHOT versions which have been a newer -SNAPSHOT version and replaces them with the latest -SNAPSHOT version. * versions:use-next-versions searches the pom for all versions which have been a newer version and replaces them with the next version. * versions:use-latest-versions searches the pom for all versions which have been a newer version and replaces them with the latest version. * versions:commit removes the pom.xml.versionsBackup files. Forms one half of the built-in Poor Man's SCM. * versions:revert restores the pom.xml files from the pom.xml.versionsBackup files. Forms one half of the built-in Poor Man's SCM. The artifacts have been deployed to the mojo repository and will be mirrored to central. The Mojo Team. Release Notes - Maven 2.x Versions Plugin - Version 1.3 ** Bug * [MVERSIONS-99] - display-dependency-updates reports dependencies with ranges under wrong heading (when the range contains the latest version) * [MVERSIONS-114] - Explict versions inside child poms are updated if they are the same than the version in the parent pom * [MVERSIONS-117] - NPE in UseLatestSnapshotsMojo when allowMajorUpdates=true * [MVERSIONS-120] - NPE from DefaultArtifactVersion.parseVersion in
maven-war-plugin 2.2 snapshot suddenly throws ClassDefError Plexus
I'm using the snapshot and am suddenly seeing this error [FATAL ERROR] Container realm = plexus.core urls[0] = file:/C:/java/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org/codehaus/plexus/archiver/jar/Manifest$ExistingAttribute org.codehaus.plexus.archiver.jar.Manifest$ExistingAttribute [INFO] [INFO] Trace java.lang.NoClassDefFoundError: org/codehaus/plexus/archiver/jar/Manifest$Existi ngAttribute at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:217 ) at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:177) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6 0) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.lang.ClassNotFoundException: org.codehaus.plexus.archiver.jar.Ma nifest$ExistingAttribute at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassL oader.java:195) -- View this message in context: http://maven.40175.n5.nabble.com/maven-war-plugin-2-2-snapshot-suddenly-throws-ClassDefError-Plexus-tp5454020p5454020.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Copying license files to my jar in maven-jar-plugin
Hi all, I have an issue with one of the Apache Incubator project when it comes to copying license files. In Apache we use apache parent pom as the main parent pom of our project. So when we use it it simply copy LICENSE,NOTICE files of its own to my jars. I have LICENSE,NOTICE files with me for each module I build. I want to override them and make sure my LICENSE,NOTICE files are there in place when jar get created. But I am having a hard time to do that, because I couldn't find proper configuration of maven-jar-plugin.. if someone can point me to all the configuration parameters of maven-jar-plugin that would be great, or please advice me how to solve this kind of an issue. Regards Lahiru -- System Analyst Programmer PTI Lab Indiana University
help - building ATG commerce using Jenkins-Maven-Artifactory
qualifier: I am an old mainframer that is new to just about everything on this side of IT we are trying to replace our ant build script with Jenkins, Maven, and Artifactory it was easy getting Jenkins to check out our code from svn but I am having difficulty telling maven where to find the ATG jar files in order to compile our ecomm code. I have not experienced it yet but I'm told it will also be a challenge to get maven to include ATG jars when creating the ear if anyone has successfully used maven for their build I would greatly appreciate seeing at least a skeleton of your pom.xml hoping I can use it as a template. thank you. CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you.
Re: help - building ATG commerce using Jenkins-Maven-Artifactory
it was easy getting Jenkins to check out our code from svn but I am having difficulty telling maven where to find the ATG jar files in order to compile our ecomm code. Put those ATG files in Artifactory. Then tell Maven about your Artifactory installation via settings.xml. It will automatically download the ATG files (assuming you put them in the project pom as a dependency) and make them available during compilation. I have not experienced it yet but I'm told it will also be a challenge to get maven to include ATG jars when creating the ear No, this should be trivial if you follow my instructions above. You will probably want to use compile scope. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: jboss-app.xml Auto Generated from MAVEN EAR plugin
Hi All, I found the correct problem. It wasn't related to DOCTYPE at all.. Wayne was correct. I have to apply this tag in MAVEN EAR plugin, The exception was coming when i try to look for WSDL for the webservice. It was throwing exception because classloader was unable to find the webservice class from the EAR. jboss version5/version loader-repositorycom.test:archive=com.test.services.ejb/loader-repository loader-repository-configjava2ParentDelegation=true/loader-repository-config /jboss Do we have any guideline or any link from where i can read which all Jboss TAG supported by MAVE EAR plugin ? Thanks. On Thu, Feb 2, 2012 at 10:31 PM, Stephen Coy st...@resolvesw.com wrote: On 03/02/2012, at 4:42 AM, Daivish Shah wrote: Hi Wayne, org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'TestEjbHandlerImpl': Invocation of init method failed; nested exception is java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/web/tomcat/service/WebCtxLoader$ENCLoader) previously initiated loading for a different type with name javax/xml/namespace/QName The whole JBoss 5 deployment descriptor is almost a red herring. In fact it exposes a clue as to what the real problem is. The problem you have here is that your application has included at least one of the (many) XML utilities out there that contains it's own version of javax.xml.namespace.QName. The reason for this is largely historical as it's generally a result of forward migration of code from Java 1.3/1.4 environments. Early xmlbeans is one such example. Old releases of Apache Axis is another source of these kinds of problems. Cheers, Steve C - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: bug in maven-jar-plugin 2.4
Hi Jane, Jane Young wrote: Hi, There is a new maven-jar-plugin 2.4 and maven-archiver 2.5 released on Feb 1st. I have a MANIFEST file that contains a very long classpath. When executing Maven 3 with maven-jar-plugin 2.4 and maven-archiver 2.5, it will fail with the following message: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:2.4:jar (default-jar) on project simple-test: Error assembling JAR: Unable to read manifest file (line too long) - [Help 1] [ERROR] This is working with previous versions of maven-jar-plugin but it's failing with maven-jar-plugin 2.4. Attached is a simple test. Can someone verify if this is bug? This is *no* bug, *your* MANIFEST is invalid (see manifest specification in JDK). The difference is that Maven uses now the JDK to read the manifest, while it did it in earlier versions on its own. So, don't expect that your jar file is working anywhere. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
