Re: ZIP and UNZIP the code source in another project
Thanks Wendy :x But does Overlay work in dev mode? It means when I modify some JSP in PROJECT-A, the PROJECT-B will be updated automatically at its deployment ( right click on PROJECT-B/ Run on server ) ? I do some tests, and I found only modified PROJECT-A's JSP files in the PROJECT-B.war, but not in real time. Luong From: Wendy Smoak wsm...@gmail.com To: Maven Users List users@maven.apache.org Sent: Fri, 18 March, 2011 15:04:34 Subject: Re: ZIP and UNZIP the code source in another project On Thu, Mar 17, 2011 at 10:08 AM, Nguyen Tien Luong tienluon...@yahoo.com wrote: Hi maven's users, Maybe the title is not understandable enough, here is my example: I have PROJECT-A which contains only JSP files. For each PROJECT-B which depends on PROJECT-A, I want that maven go and get the JSP files in PROJECT-A and put in PROJECT-B with same folder's structure. Given that these are JSP files I assume this is a webapp. If you - make A a war file, which will be mostly empty, with the JSP files in the right layout - in B, declare a dependency on A with typewar/type Maven will treat the war type dependency as an overlay and automatically copy in the JSP files from A. http://maven.apache.org/plugins/maven-war-plugin/overlays.html -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
how to release without distributionManagement
Hello, I have a project for which I do not really need a site or for that matter a distributionManagement ... is there a way to successfully release i.e. branch out etc etc without having to specify a distributionManagement? TIA, Best regards, Giovanni -- View this message in context: http://maven.40175.n5.nabble.com/how-to-release-without-distributionManagement-tp4166131p4166131.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: multi module support
I just created a web project in myeclipse 8 and I use maven Support So I added JSF and ICEfaces capabilities in my project I put a single home page in the project but when I deployed the project in of myeclipse tomcat (I tried the same thing by installing Tomcat7) when I start the server it gives me errors I have not understood or it come!! is that you have a proposal about?! Error : 19 mars 2011 11:13:32 org.apache.catalina.core.AprLifecycleListener init INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Common Files\MyEclipse\binary\com.sun.java.jdk.win32.x86_1.6.0.013\bin;C:\Program Files\Common Files\MyEclipse\plugins\com.genuitec.eclipse.easie.tomcat.myeclipse_8.6.0.me201007231647\tomcat\bin 19 mars 2011 11:13:32 org.apache.coyote.http11.Http11Protocol init INFO: Initialisation de Coyote HTTP/1.1 sur http-8080 19 mars 2011 11:13:32 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 798 ms 19 mars 2011 11:13:32 org.apache.catalina.core.StandardService start INFO: Démarrage du service Catalina 19 mars 2011 11:13:32 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.13 19 mars 2011 11:13:34 com.sun.faces.config.ConfigureListener contextInitialized INFO: Initializing Sun's JavaServer Faces implementation (1.2_04-b07-FCS) for context '/criam-web' 19 mars 2011 11:13:34 com.icesoft.faces.application.ViewRootStateManagerImpl INFO: ViewRootStateManagerImpl constructed with Delegate: com.sun.faces.application.StateManagerImpl@1ba0f36 19 mars 2011 11:13:34 com.icesoft.faces.application.D2DViewHandler INFO: ICEsoft Technologies, Inc. ICEfaces 1.8.1 Build number: 7 Revision: 18926 19 mars 2011 11:13:35 org.apache.catalina.core.StandardContext listenerStart GRAVE: Exception lors de l'envoi de l'évènement contexte initialisé (context initialized) à l'instance de classe d'écoute (listener) com.sun.faces.config.ConfigureListener java.lang.LinkageError: loader constraint violation: when resolving interface method javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory; the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, com/sun/faces/config/ConfigureListener, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ExpressionFactory used in the signature at com.sun.faces.config.ConfigureListener.registerELResolverAndListenerWithJsp(ConfigureListener.java:1628) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:453) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:566) 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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) 19 mars 2011 11:13:35 org.apache.catalina.core.StandardContext start GRAVE: Error listenerStart 19 mars 2011 11:13:35 org.apache.catalina.core.StandardContext start GRAVE: Erreur de démarrage du contexte [/criam-web] suite aux erreurs précédentes 19 mars 2011 11:13:35
[ANN] Maven Findbugs plugin version 2.3.2 Released
Hi, The Mojo team is pleased to announce the release of the Maven FindBugs Plugin version 2.3.2. FindBugs uses static analysis to inspect Java bytecode for occurrences of bug patterns. You can see more about the plugin at: http://mojo.codehaus.org/findbugs-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdfindbugs-maven-plugin/artifactId version2.3.2/version /plugin Release Notes are at: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11701version=16025 Release Notes - Maven 2.x FindBugs Plugin - Version 2.3.2 ** Bug * [MFINDBUGS-109] - empty surefire report at the project site having findBugs in the reporting section * [MFINDBUGS-111] - Missing Bad Practice entries * [MFINDBUGS-112] - failOnError not being honored * [MFINDBUGS-113] - Inner classes are badly encoded in XML reports * [MFINDBUGS-122] - [Maven3] Could not find matching constructor for: org.codehaus.mojo.findbugs.FindbugsReportGenerator * [MFINDBUGS-126] - org.codehaus.mojo.findbugs.FindbugsReportGenerator(org.codehaus.doxia.module.xhtml.XhtmlSink * [MFINDBUGS-127] - Xref links are not generated with Maven 3 * [MFINDBUGS-128] - Empty classes in FindBugs report * [MFINDBUGS-132] - Findbugs doesn't run on projects containing only test classes * [MFINDBUGS-134] - Problems resolving pluginList ** Improvement * [MFINDBUGS-110] - Major performance degradation since FindBugs plugin 2.1 * [MFINDBUGS-119] - Update to GMaven 1.3 (to fix maven 3 build) * [MFINDBUGS-121] - The FindBugs documentation for parameters is verys sparse and should be improved * [MFINDBUGS-130] - Site doc pages refer to downlevel plugin version * [MFINDBUGS-133] - Add the ability to have multiple exclude filter files ** Wish * [MFINDBUGS-129] - maven3 Enjoy, The Mojo team. Garvin LeClaire glecla...@insightbb.com
maven with ICEFACES
I just created a web project in myeclipse 8 and I use maven Support So I added JSF and ICEfaces capabilities in my project I put a single home page in the project but when I deployed the project in of myeclipse tomcat (I tried the same thing by installing Tomcat7) when I start the server it gives me errors I have not understood or it come!! is that you have a proposal about?! Error : 19 mars 2011 11:13:32 org.apache.catalina.core.AprLifecycleListener init INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Common Files\MyEclipse\binary\com.sun.java.jdk.win32.x86_1.6.0.013\bin;C:\Program Files\Common Files\MyEclipse\plugins\com.genuitec.eclipse.easie.tomcat.myeclipse_8.6.0.me201007231647\tomcat\bin 19 mars 2011 11:13:32 org.apache.coyote.http11.Http11Protocol init INFO: Initialisation de Coyote HTTP/1.1 sur http-8080 19 mars 2011 11:13:32 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 798 ms 19 mars 2011 11:13:32 org.apache.catalina.core.StandardService start INFO: Démarrage du service Catalina 19 mars 2011 11:13:32 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.13 19 mars 2011 11:13:34 com.sun.faces.config.ConfigureListener contextInitialized INFO: Initializing Sun's JavaServer Faces implementation (1.2_04-b07-FCS) for context '/criam-web' 19 mars 2011 11:13:34 com.icesoft.faces.application.ViewRootStateManagerImpl INFO: ViewRootStateManagerImpl constructed with Delegate: com.sun.faces.application.StateManagerImpl@1ba0f36 19 mars 2011 11:13:34 com.icesoft.faces.application.D2DViewHandler INFO: ICEsoft Technologies, Inc. ICEfaces 1.8.1 Build number: 7 Revision: 18926 19 mars 2011 11:13:35 org.apache.catalina.core.StandardContext listenerStart GRAVE: Exception lors de l'envoi de l'évènement contexte initialisé (context initialized) à l'instance de classe d'écoute (listener) com.sun.faces.config.ConfigureListener java.lang.LinkageError: loader constraint violation: when resolving interface method javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory; the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, com/sun/faces/config/ConfigureListener, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ExpressionFactory used in the signature at com.sun.faces.config.ConfigureListener.registerELResolverAndListenerWithJsp(ConfigureListener.java:1628) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:453) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:566) 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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) 19 mars 2011 11:13:35 org.apache.catalina.core.StandardContext start GRAVE: Error listenerStart 19 mars 2011 11:13:35 org.apache.catalina.core.StandardContext start GRAVE: Erreur de démarrage du contexte [/criam-web] suite aux erreurs précédentes 19 mars 2011 11:13:35
Re: multi module support
I would think that myeclipse knowledge on this generic Maven mailing list is (very) limited. You should ask your question somewhere else, although I have no clue where. /Anders On Sun, Mar 20, 2011 at 23:24, inforedaster inforedas...@gmail.com wrote: I just created a web project in myeclipse 8 and I use maven Support So I added JSF and ICEfaces capabilities in my project I put a single home page in the project but when I deployed the project in of myeclipse tomcat (I tried the same thing by installing Tomcat7) when I start the server it gives me errors I have not understood or it come!! is that you have a proposal about?! Error : 19 mars 2011 11:13:32 org.apache.catalina.core.AprLifecycleListener init INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Common Files\MyEclipse\binary\com.sun.java.jdk.win32.x86_1.6.0.013\bin;C:\Program Files\Common Files\MyEclipse\plugins\com.genuitec.eclipse.easie.tomcat.myeclipse_8.6.0.me201007231647\tomcat\bin 19 mars 2011 11:13:32 org.apache.coyote.http11.Http11Protocol init INFO: Initialisation de Coyote HTTP/1.1 sur http-8080 19 mars 2011 11:13:32 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 798 ms 19 mars 2011 11:13:32 org.apache.catalina.core.StandardService start INFO: Démarrage du service Catalina 19 mars 2011 11:13:32 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.13 19 mars 2011 11:13:34 com.sun.faces.config.ConfigureListener contextInitialized INFO: Initializing Sun's JavaServer Faces implementation (1.2_04-b07-FCS) for context '/criam-web' 19 mars 2011 11:13:34 com.icesoft.faces.application.ViewRootStateManagerImpl INFO: ViewRootStateManagerImpl constructed with Delegate: com.sun.faces.application.StateManagerImpl@1ba0f36 19 mars 2011 11:13:34 com.icesoft.faces.application.D2DViewHandler INFO: ICEsoft Technologies, Inc. ICEfaces 1.8.1 Build number: 7 Revision: 18926 19 mars 2011 11:13:35 org.apache.catalina.core.StandardContext listenerStart GRAVE: Exception lors de l'envoi de l'évènement contexte initialisé (context initialized) à l'instance de classe d'écoute (listener) com.sun.faces.config.ConfigureListener java.lang.LinkageError: loader constraint violation: when resolving interface method javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory; the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, com/sun/faces/config/ConfigureListener, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ExpressionFactory used in the signature at com.sun.faces.config.ConfigureListener.registerELResolverAndListenerWithJsp(ConfigureListener.java:1628) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:453) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:566) 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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) 19 mars 2011 11:13:35
Re: how to release without distributionManagement
Well, if you're going to do a release you do need the repo you would do that to defined in distMgmt. That being said, I'm guessing it should be the same as for all other releases of this project so you shouldn't need to change anything. Or? /Anders On Mon, Mar 21, 2011 at 02:18, bravegag brave...@gmail.com wrote: Hello, I have a project for which I do not really need a site or for that matter a distributionManagement ... is there a way to successfully release i.e. branch out etc etc without having to specify a distributionManagement? TIA, Best regards, Giovanni -- View this message in context: http://maven.40175.n5.nabble.com/how-to-release-without-distributionManagement-tp4166131p4166131.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
[maven-war-plugin] Exclude files/folders in webapp
Hi maven'users, Can we, in using maven-war-plugin, exclude files/folders in webapp? Here my exemple: webapp ++ admin index.jsp admin.jsp ++ client index.jsp account.jsp META-INF WEB-INF Anf I don't want that the client's folder appear in my final WAR. Thanks, Luong
Re: [maven-war-plugin] Exclude files/folders in webapp
How about warSourceExcludes options [1]? Btw, why these files are there if you don't want them to appear in WAR? 1. http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#warSourceExcludes — Yegor Bugayenko On Mon, Mar 21, 2011 at 10:28 AM, Nguyen Tien Luong tienluon...@yahoo.comwrote: Hi maven'users, Can we, in using maven-war-plugin, exclude files/folders in webapp? Here my exemple: webapp ++ admin index.jsp admin.jsp ++ client index.jsp account.jsp META-INF WEB-INF Anf I don't want that the client's folder appear in my final WAR. Thanks, Luong
Re: how to release without distributionManagement
Hi, I already specify the SCM in two places actually: in the pom.xml scm:svn:https://svn.vis.ethz.ch/svn/webengineering scm:svn:https://svn.vis.ethz.ch/svn/webengineering http://svn.vis.ethz.ch/svn/webengineering another place is the command line: mvn release:perform -DconnectionUrl=scm:svn:https://svn.vis.ethz.ch/svn/webengineering/trunk -DtagBase=file:Users/bravegag/code/webengineering/tags So I don't understand why is needed yet another way to specify the repository. AFAIK distributionManagement is used to specify the target of the project report and web site but I don't want/need any. TIA, Best regards, Giovanni -- View this message in context: http://maven.40175.n5.nabble.com/how-to-release-without-distributionManagement-tp4166131p4221269.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: Unwanted jars getting copied
Hi Hilco ,
Sorry for the late reply.
Here is the complete pom.xml. The problem is rt.jar and tools.jar are getting
added in war file which we don’t want.
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/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.nielsen.outbound/groupId
artifactIdoutbound/artifactId
version1.0-SNAPSHOT/version
packagingwar/packaging
nameoutbound/name
urlhttp://maven.apache.org/url
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
server.dir/Tomcat6/webapps//server.dir
war.nameoutbound/war.name
webapp.dir${project.build.directory}/work/outbound/webapp.dir
/properties
dependencies
dependency
groupIdcom.nielsen.online.iat/groupId
artifactIdinfrastructure/artifactId
version1.1/version
/dependency
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version4.4/version
scopetest/scope
/dependency
dependency
groupIdlog4j/groupId
artifactIdlog4j/artifactId
version1.2.14/version
scopeprovided/scope
/dependency
dependency
groupIdjavax.ws/groupId
artifactIdjersey-core/artifactId
version1.1.5/version
scopeprovided/scope
/dependency
dependency
groupIdjavax.ws/groupId
artifactIdjersey-client/artifactId
version1.1.5/version
scopeprovided/scope
/dependency
dependency
groupIdcom.sun.jsr/groupId
artifactIdjsr311-api/artifactId
version1.0/version
scopeprovided/scope
/dependency
dependency
groupIdcom.sun.jsr/groupId
artifactIdjsr311-api/artifactId
version1.1/version
scopeprovided/scope
/dependency
dependency
groupIdorg.google/groupId
artifactIdcore4j/artifactId
version0.3/version
/dependency
dependency
groupIdorg.google/groupId
artifactIdodata4j/artifactId
version1.0/version
/dependency
dependency
groupIdcommons-lang/groupId
artifactIdcommons-lang/artifactId
version2.4/version
scopeprovided/scope
/dependency
dependency
groupIdcommons-discovery/groupId
artifactIdcommons-discovery/artifactId
version0.2/version
/dependency
dependency
groupIdnet.sf.ehcache/groupId
artifactIdehcache/artifactId
version1.5.0/version
scopeprovided/scope
/dependency
dependency
groupIdcom.sun.jersey.api/groupId
artifactIdcore/artifactId
version1.1.5/version
scopeprovided/scope
/dependency
dependency
groupIdorg/groupId
artifactIdjson/artifactId
version1.0/version
scopeprovided/scope
/dependency
dependency
groupIdcom.sun.jersey/groupId
artifactIdserver/artifactId
version1.1.5/version
scopeprovided/scope
/dependency
dependency
groupIdbackport-util-concurrent/groupId
artifactIdbackport-util-concurrent/artifactId
version3.0/version
scopeprovided/scope
/dependency
dependency
groupIdorg.apache.axis/groupId
artifactIdaxis-jaxrpc/artifactId
version1.4/version
Re: how to release without distributionManagement
distributionManagement is the target for the Maven artifacts. release:perform calls deploy as default, and deploy needs the distributionManagement. If you do not want this (e.g. only install the Maven artifact in the local repository), then you have to do something like this: plugin artifactIdmaven-release-plugin/artifactId version2.1/version configuration goalsinstall/goals /configuration /plugin http://maven.apache.org/plugins/maven-release-plugin/examples/perform-release.html Manuel On Mon, Mar 21, 2011 at 10:49, bravegag brave...@gmail.com wrote: Hi, I already specify the SCM in two places actually: in the pom.xml scm:svn:https://svn.vis.ethz.ch/svn/webengineering scm:svn:https://svn.vis.ethz.ch/svn/webengineering http://svn.vis.ethz.ch/svn/webengineering another place is the command line: mvn release:perform -DconnectionUrl=scm:svn:https://svn.vis.ethz.ch/svn/webengineering/trunk -DtagBase=file:Users/bravegag/code/webengineering/tags So I don't understand why is needed yet another way to specify the repository. AFAIK distributionManagement is used to specify the target of the project report and web site but I don't want/need any. TIA, Best regards, Giovanni -- View this message in context: http://maven.40175.n5.nabble.com/how-to-release-without-distributionManagement-tp4166131p4221269.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
jetty parent pom plugin declaration and child pom plugin redefinition
Hi, I declare a jetty plugin in my parent pom. I have some web-apps (child of the parent pom) that will deployed to diferents jetty servers with diferent set of extra jars (each webapp have a diferent set of provided dependency). I can't redefine my parent pom jetty plugin definition in each web app pom with diferent set of extra jars, accord to provided dependency of each webapp. What is the way? Thank you!, Diego
Re: multi module support
This error indicates that your application deploys a version of el-api.jar in WEB-INF/lib which conflicts with the built-in version in tomcat. You should manually delete this jar file from the target directory each time you do a (eclipse based) deployment to tomcat, as to my knowledge declaring scopeprovided/scope for el-api.jar will not be sufficient to prevent deploying this artifact. I think this is due to a bug in the m2eclipse WTP integration. And yes, i think this question should have been asked in the m2eclipse or myeclipse forums. Hope this helps, Torsten On 20.03.2011 23:24, inforedaster [via Maven] wrote: I just created a web project in myeclipse 8 and I use maven Support So I added JSF and ICEfaces capabilities in my project I put a single home page in the project but when I deployed the project in of myeclipse tomcat (I tried the same thing by installing Tomcat7) when I start the server it gives me errors I have not understood or it come!! is that you have a proposal about?! Error : 19 mars 2011 11:13:32 org.apache.catalina.core.AprLifecycleListener init INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Common Files\MyEclipse\binary\com.sun.java.jdk.win32.x86_1.6.0.013\bin;C:\Program Files\Common Files\MyEclipse\plugins\com.genuitec.eclipse.easie.tomcat.myeclipse_8.6.0.me201007231647\tomcat\bin 19 mars 2011 11:13:32 org.apache.coyote.http11.Http11Protocol init INFO: Initialisation de Coyote HTTP/1.1 sur http-8080 19 mars 2011 11:13:32 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 798 ms 19 mars 2011 11:13:32 org.apache.catalina.core.StandardService start INFO: Démarrage du service Catalina 19 mars 2011 11:13:32 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.13 19 mars 2011 11:13:34 com.sun.faces.config.ConfigureListener contextInitialized INFO: Initializing Sun's JavaServer Faces implementation (1.2_04-b07-FCS) for context '/criam-web' 19 mars 2011 11:13:34 com.icesoft.faces.application.ViewRootStateManagerImpl INFO: ViewRootStateManagerImpl constructed with Delegate: com.sun.faces.application.StateManagerImpl@1ba0f36 19 mars 2011 11:13:34 com.icesoft.faces.application.D2DViewHandler INFO: ICEsoft Technologies, Inc. ICEfaces 1.8.1 Build number: 7 Revision: 18926 19 mars 2011 11:13:35 org.apache.catalina.core.StandardContext listenerStart GRAVE: Exception lors de l'envoi de l'évènement contexte initialisé (context initialized) à l'instance de classe d'écoute (listener) com.sun.faces.config.ConfigureListener java.lang.LinkageError: loader constraint violation: when resolving interface method javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory; the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, com/sun/faces/config/ConfigureListener, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ExpressionFactory used in the signature at com.sun.faces.config.ConfigureListener.registerELResolverAndListenerWithJsp(ConfigureListener.java:1628) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:453) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:566) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
Re: Unwanted jars getting copied
Hi Amol,
The rt.jar and tools.jar maybe be transitively referenced in your project.
Try mvn dependency:tree on your project. This will list all the
dependencies in a hierarchy. You can find which exact dependency is
referencing the rt.jar and tools.jar libraries.
It is questionable why rt.jar would referenced by some project. I have
seen tools.jar being referenced in some open source projects.
If I was writing a pom which needs rt.jar or tools.jar, I would define
the scope as provided, so if you can control the pom of a dependency
referencing these jars, change the dependencies to have scope provided.
In case these are a being referenced by some of the third party
libraries and you cannot change the pom.xml, use dependency exclusion.
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-core/artifactId
version2.4.0/version
exclusions
exclusion
groupIdcom.sun/groupId
artifactIdtools/artifactId
/exclusion
/exclusions
/dependency
Hi Hilco ,
Sorry for the late reply.
Here is the complete pom.xml. The problem is rt.jar and tools.jar are getting
added in war file which we don’t want.
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/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.nielsen.outbound/groupId
artifactIdoutbound/artifactId
version1.0-SNAPSHOT/version
packagingwar/packaging
nameoutbound/name
urlhttp://maven.apache.org/url
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
server.dir/Tomcat6/webapps//server.dir
war.nameoutbound/war.name
webapp.dir${project.build.directory}/work/outbound/webapp.dir
/properties
dependencies
dependency
groupIdcom.nielsen.online.iat/groupId
artifactIdinfrastructure/artifactId
version1.1/version
/dependency
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version4.4/version
scopetest/scope
/dependency
dependency
groupIdlog4j/groupId
artifactIdlog4j/artifactId
version1.2.14/version
scopeprovided/scope
/dependency
dependency
groupIdjavax.ws/groupId
artifactIdjersey-core/artifactId
version1.1.5/version
scopeprovided/scope
/dependency
dependency
groupIdjavax.ws/groupId
artifactIdjersey-client/artifactId
version1.1.5/version
scopeprovided/scope
/dependency
dependency
groupIdcom.sun.jsr/groupId
artifactIdjsr311-api/artifactId
version1.0/version
scopeprovided/scope
/dependency
dependency
groupIdcom.sun.jsr/groupId
artifactIdjsr311-api/artifactId
version1.1/version
scopeprovided/scope
/dependency
dependency
groupIdorg.google/groupId
artifactIdcore4j/artifactId
version0.3/version
/dependency
dependency
groupIdorg.google/groupId
artifactIdodata4j/artifactId
version1.0/version
/dependency
dependency
groupIdcommons-lang/groupId
artifactIdcommons-lang/artifactId
version2.4/version
scopeprovided/scope
/dependency
dependency
groupIdcommons-discovery/groupId
artifactIdcommons-discovery/artifactId
version0.2/version
/dependency
dependency
groupIdnet.sf.ehcache/groupId
artifactIdehcache/artifactId
version1.5.0/version
scopeprovided/scope
/dependency
dependency
groupIdcom.sun.jersey.api/groupId
artifactIdcore/artifactId
version1.1.5/version
scopeprovided/scope
Test phase for a command line tool (resend)
Note: I sent this on Friday (2011-03-18) but saw no response, so am resending on the chance that it somehow got lost in transit. Caveat: I am new to Maven. I've read the online documentation but haven't found a good source of sample POMs other than for very basic configurations. I have a POM that builds a command-line tool. I figured out how to use the assembly plugin to build a self-contained jar, but now I need to be able to run a series of test cases using that jar and a custom shell script to invoke it. I have several questions: 1) Where do I put my custom shell script in the hierarchy? I've put the source into src/main/bin for now. 2) For testing I'd like to copy the shell script and self-contained jar (jar-with-dependencies) to a test directory (similar to test-classes) and run the jar from there. How do I do that? 3) The command-line tool analyzes compiled Java code from a jar and builds an XML file from the analysis. What I'd like to do for my test cases is compile a bunch of different tests into different jars, then for each jar run the tool over it, generating an XML file, and do a diff on the XML file against expected output. How do I do that? 3a) Alternatively I could write a test application that used Runtime.exec() to run the tool for each test case, then read in the resulting XML files using an XML parser and made a bunch of assertions about each file, but frankly I'd rather avoid writing the extra code. If I need to, however, how would I do that? I don't necessarily need the actual POMs written for me; pointers to more complete samples doing similar tasks would be fine. Thanks in advance. -- Rick Genter rgen...@interactions.net *** This e-mail and any of its attachments may contain Interactions Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Interactions Corporation. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You. *** - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Test phase for a command line tool (resend)
Hi! You may some basic poms at my blog, http://thomassundberg.wordpress.com/ I would locate a test script in the project root and have it to point to a self-contained jar in ./target Another option would be to use the Resource plugin, http://maven.apache.org/plugins/maven-resources-plugin/ and locate the script in any good directory under src. HTH Thomas On Mon, Mar 21, 2011 at 14:24, Rick Genter rgen...@interactions.net wrote: Note: I sent this on Friday (2011-03-18) but saw no response, so am resending on the chance that it somehow got lost in transit. Caveat: I am new to Maven. I've read the online documentation but haven't found a good source of sample POMs other than for very basic configurations. I have a POM that builds a command-line tool. I figured out how to use the assembly plugin to build a self-contained jar, but now I need to be able to run a series of test cases using that jar and a custom shell script to invoke it. I have several questions: 1) Where do I put my custom shell script in the hierarchy? I've put the source into src/main/bin for now. 2) For testing I'd like to copy the shell script and self-contained jar (jar-with-dependencies) to a test directory (similar to test-classes) and run the jar from there. How do I do that? 3) The command-line tool analyzes compiled Java code from a jar and builds an XML file from the analysis. What I'd like to do for my test cases is compile a bunch of different tests into different jars, then for each jar run the tool over it, generating an XML file, and do a diff on the XML file against expected output. How do I do that? 3a) Alternatively I could write a test application that used Runtime.exec() to run the tool for each test case, then read in the resulting XML files using an XML parser and made a bunch of assertions about each file, but frankly I'd rather avoid writing the extra code. If I need to, however, how would I do that? I don't necessarily need the actual POMs written for me; pointers to more complete samples doing similar tasks would be fine. Thanks in advance. -- Rick Genter rgen...@interactions.net *** This e-mail and any of its attachments may contain Interactions Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Interactions Corporation. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You. *** - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Thomas Sundberg M. Sc. in Computer Science Mobile: +46 70 767 33 15 Blog: http://thomassundberg.wordpress.com/ Twitter: @thomassundberg Better software through faster feedback
Re: [maven-war-plugin] Exclude files/folders in webapp
Thanks Yegor, The reason is in client's folder, there are only some files that I use locally and I don't want put them in the release :D and as you said, warSourceExcludes works :x artifactIdmaven-war-plugin/artifactId version2.1.1/version configuration warSourceExcludes**/client/*.*/warSourceExcludes /configuration /plugin Thanks again :x Luong From: Yegor Bugayenko e...@technoparkcorp.com To: Maven Users List users@maven.apache.org Cc: Nguyen Tien Luong tienluon...@yahoo.com Sent: Mon, 21 March, 2011 10:42:31 Subject: Re: [maven-war-plugin] Exclude files/folders in webapp How about warSourceExcludes options [1]? Btw, why these files are there if you don't want them to appear in WAR? 1. http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#warSourceExcludes — Yegor Bugayenko On Mon, Mar 21, 2011 at 10:28 AM, Nguyen Tien Luong tienluon...@yahoo.comwrote: Hi maven'users, Can we, in using maven-war-plugin, exclude files/folders in webapp? Here my exemple: webapp ++ admin index.jsp admin.jsp ++ client index.jsp account.jsp META-INF WEB-INF Anf I don't want that the client's folder appear in my final WAR. Thanks, Luong
Re: Test phase for a command line tool (resend)
I would integrate these integration tests into the build itself. Either in the maven Project itself (if you only have one project) or in a separate module. You can use the maven-invoker-plugin for example to execute the integration tests (along with creating all necessary jars, or whatever, that you need for the tests). /Anders On Mon, Mar 21, 2011 at 14:38, Thomas Sundberg t...@kth.se wrote: Hi! You may some basic poms at my blog, http://thomassundberg.wordpress.com/ I would locate a test script in the project root and have it to point to a self-contained jar in ./target Another option would be to use the Resource plugin, http://maven.apache.org/plugins/maven-resources-plugin/ and locate the script in any good directory under src. HTH Thomas On Mon, Mar 21, 2011 at 14:24, Rick Genter rgen...@interactions.net wrote: Note: I sent this on Friday (2011-03-18) but saw no response, so am resending on the chance that it somehow got lost in transit. Caveat: I am new to Maven. I've read the online documentation but haven't found a good source of sample POMs other than for very basic configurations. I have a POM that builds a command-line tool. I figured out how to use the assembly plugin to build a self-contained jar, but now I need to be able to run a series of test cases using that jar and a custom shell script to invoke it. I have several questions: 1) Where do I put my custom shell script in the hierarchy? I've put the source into src/main/bin for now. 2) For testing I'd like to copy the shell script and self-contained jar (jar-with-dependencies) to a test directory (similar to test-classes) and run the jar from there. How do I do that? 3) The command-line tool analyzes compiled Java code from a jar and builds an XML file from the analysis. What I'd like to do for my test cases is compile a bunch of different tests into different jars, then for each jar run the tool over it, generating an XML file, and do a diff on the XML file against expected output. How do I do that? 3a) Alternatively I could write a test application that used Runtime.exec() to run the tool for each test case, then read in the resulting XML files using an XML parser and made a bunch of assertions about each file, but frankly I'd rather avoid writing the extra code. If I need to, however, how would I do that? I don't necessarily need the actual POMs written for me; pointers to more complete samples doing similar tasks would be fine. Thanks in advance. -- Rick Genter rgen...@interactions.net *** This e-mail and any of its attachments may contain Interactions Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Interactions Corporation. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You. *** - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Thomas Sundberg M. Sc. in Computer Science Mobile: +46 70 767 33 15 Blog: http://thomassundberg.wordpress.com/ Twitter: @thomassundberg Better software through faster feedback
Re: [maven-war-plugin] Exclude files/folders in webapp
I'm still thinking that it's a wrong approach to keep something inside webapp directory which is not going to be distributed as part of your WAR file. Instead, you can use src/test/resources/webapp directory, if these files are required for in-container testing only. Or maybe you can create another sub-module for your client sub-project. Anyway, I'm happy it works now with warSourceExcludes. — Yegor Bugayenko On Mon, Mar 21, 2011 at 2:51 PM, Nguyen Tien Luong tienluon...@yahoo.comwrote: Thanks Yegor, The reason is in client's folder, there are only some files that I use locally and I don't want put them in the release :D and as you said, warSourceExcludes works :x artifactIdmaven-war-plugin/artifactId version2.1.1/version configuration warSourceExcludes**/client/*.*/warSourceExcludes /configuration /plugin Thanks again :x Luong From: Yegor Bugayenko e...@technoparkcorp.com To: Maven Users List users@maven.apache.org Cc: Nguyen Tien Luong tienluon...@yahoo.com Sent: Mon, 21 March, 2011 10:42:31 Subject: Re: [maven-war-plugin] Exclude files/folders in webapp How about warSourceExcludes options [1]? Btw, why these files are there if you don't want them to appear in WAR? 1. http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#warSourceExcludes — Yegor Bugayenko On Mon, Mar 21, 2011 at 10:28 AM, Nguyen Tien Luong tienluon...@yahoo.comwrote: Hi maven'users, Can we, in using maven-war-plugin, exclude files/folders in webapp? Here my exemple: webapp ++ admin index.jsp admin.jsp ++ client index.jsp account.jsp META-INF WEB-INF Anf I don't want that the client's folder appear in my final WAR. Thanks, Luong
RE: Test phase for a command line tool (resend)
MGhopefully quick response
From: rgen...@interactions.net
Subject: Test phase for a command line tool (resend)
Date: Mon, 21 Mar 2011 09:24:27 -0400
CC: rgen...@interactions.net
To: users@maven.apache.org
Note: I sent this on Friday (2011-03-18) but saw no response, so am resending
on the chance that it somehow got lost in transit.
Caveat: I am new to Maven. I've read the online documentation but haven't
found a good source of sample POMs other than for very basic configurations.
I have a POM that builds a command-line tool. I figured out how to use the
assembly plugin to build a self-contained jar, but now I need to be able to
run a series of test cases using that jar and a custom shell script to invoke
it. I have several questions:
1) Where do I put my custom shell script in the hierarchy? I've put the
source into src/main/bin for now.
MGanywhere you want to as long as you chmod +execute for that folder
2) For testing I'd like to copy the shell script and self-contained jar
(jar-with-dependencies) to a test directory (similar to test-classes) and run
the jar from there. How do I do that?
MGgenerally in process-resources phase e.g.
build
plugins
plugin
groupIdPlugin-groupId/plugin
artifactIdplugin-artifactId/artifactId
versionplugin-version/version
executions
execution
idprocess-resources/id
phaseprocess-resources/phase
configuration
tasks
tstamp
format property=build.time pattern=MMM
dd, (hh:mm:ss z) locale=en /
/tstamp
copy toDir=${basedir}/target/classes/
overwrite=true filtering=on
!-- this will only include files with the
xsl extension from ${basedir}/src --
fileset dir=${basedir}/src/
includes=**/*.xsl /
/copy
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
/build
3) The command-line tool analyzes compiled Java code from a jar and builds an
XML file from the analysis. What I'd like to do for my test cases is compile
a bunch of different tests into different jars, then for each jar run the
tool over it, generating an XML file, and do a diff on the XML file against
expected output. How do I do that?
MGcygwin has a nice diff tool which you can use
MGC:\maven-plugin\axis2-aar-maven-plugin\src\modules\codegendiff --help
MGUsage: diff [OPTION]... FILES
MG-r for recursive
MGFILES are `FILE1 FILE2' or `DIR1 DIR2' or `DIR FILE...' or `FILE... DIR'.
MGIf --from-file or --to-file is given, there are no restrictions on FILES.
MGIf a FILE is `-', read standard input.
MGExit status is 0 if inputs are the same, 1 if different, 2 if trouble.
MGyou can use the maven-antrun-plugin and inside build.xml have a default
target which runs
MGexec diff FILE1 FILE2
3a) Alternatively I could write a test application that used Runtime.exec()
to run the tool for each test case, then read in the resulting XML files
using an XML parser and made a bunch of assertions about each file, but
frankly I'd rather avoid writing the extra code. If I need to, however, how
would I do that?
MGmaven-antrun-plugin and inside build.xml have a target which runs
MGjava -jar WhateverNameOfJarFile input
I don't necessarily need the actual POMs written for me; pointers to more
complete samples doing similar tasks would be fine. Thanks in advance.
--
Rick Genter
rgen...@interactions.net
***
This e-mail and any of its attachments may contain Interactions Corporation
proprietary information, which is privileged, confidential, or subject to
copyright belonging to the Interactions Corporation. This e-mail is intended
solely for the use of the individual or entity to which it is addressed. If
you
are not the intended recipient of this e-mail, you are hereby notified that
any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this e-mail is strictly prohibited and may be
unlawful. If you have received this e-mail in error, please notify the sender
immediately and permanently delete the original and any copy of this e-mail
and
any printout. Thank You.
***
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
Reopen MPIR-180 (Repositories which require authentication get blacklisted)?
Hi all, My internal repository requires an authentication. When I build the Dependencies report with : mvn org.apache.maven.plugins:maven-project-info-reports-plugin:2.3:dependencies -- No problem, it works fine. but with : mvn org.apache.maven.plugins:maven-project-info-reports-plugin:2.3.1:dependencies -- my repository is blacklisted again, as with the older plugin versions ( 2.2) http://jira.codehaus.org/browse/MPIR-180 Am I alone in this case? (I'm using maven 3.0.2) Thanks Thierry -- View this message in context: http://maven.40175.n5.nabble.com/Reopen-MPIR-180-Repositories-which-require-authentication-get-blacklisted-tp4229472p4229472.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
Adding files to target before creating war
Hi, I'm pretty new to Maven user but have been using it in a simple case for a while now to create a web based project. Currently I use war:exploded for local development and install for creating a distributable. I'm now in a situation where I want to overwrite some standard files (properties, etc) for certain profiles. I was hoping I could do this with antrun. I origionally bound the plugin to run at the prepare-package phase but it looks as if this is too early. The target directory gets created after this and the copied files are over ridden. Is there a way I can run this after the target directory is created but before the war is built? Thanks, Sam - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding files to target before creating war
The target directory is probably created in the generate-resources phase, before the compile phase. What about trying it in the package phase? You can also try the pre-integration-test phase, but this will only be called if you run maven with a target higher than package. Here are the various phases, scroll down to Default Lifecycle: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html Csaba On 21.3.2011 15:55, Sam Adams wrote: Hi, I'm pretty new to Maven user but have been using it in a simple case for a while now to create a web based project. Currently I use war:exploded for local development and install for creating a distributable. I'm now in a situation where I want to overwrite some standard files (properties, etc) for certain profiles. I was hoping I could do this with antrun. I origionally bound the plugin to run at the prepare-package phase but it looks as if this is too early. The target directory gets created after this and the copied files are over ridden. Is there a way I can run this after the target directory is created but before the war is built? Thanks, Sam - 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: Adding files to target before creating war
It seems that the target isn't created until the package phase, this is also when the war is created. Is there any kind of finer grained control over when plugins are run? Thanks, Sam On 21 March 2011 15:07, Gajo Csaba csaba.g...@cosylab.com wrote: The target directory is probably created in the generate-resources phase, before the compile phase. What about trying it in the package phase? You can also try the pre-integration-test phase, but this will only be called if you run maven with a target higher than package. Here are the various phases, scroll down to Default Lifecycle: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html Csaba On 21.3.2011 15:55, Sam Adams wrote: Hi, I'm pretty new to Maven user but have been using it in a simple case for a while now to create a web based project. Currently I use war:exploded for local development and install for creating a distributable. I'm now in a situation where I want to overwrite some standard files (properties, etc) for certain profiles. I was hoping I could do this with antrun. I origionally bound the plugin to run at the prepare-package phase but it looks as if this is too early. The target directory gets created after this and the copied files are over ridden. Is there a way I can run this after the target directory is created but before the war is built? Thanks, Sam - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding files to target before creating war
On Mon, Mar 21, 2011 at 10:55 AM, Sam Adams sbad...@gmail.com wrote: I'm now in a situation where I want to overwrite some standard files (properties, etc) for certain profiles. What problem are you trying to solve? It sounds like you're using profiles to produce *different* war files depending on what gets activated, which is generally not a good idea. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding files to target before creating war
This is exactly what I'm trying to do. Why is this not a good idea and what are the alternatives? Thanks, Sam On 21 March 2011 15:19, Wendy Smoak wsm...@gmail.com wrote: On Mon, Mar 21, 2011 at 10:55 AM, Sam Adams sbad...@gmail.com wrote: I'm now in a situation where I want to overwrite some standard files (properties, etc) for certain profiles. What problem are you trying to solve? It sounds like you're using profiles to produce *different* war files depending on what gets activated, which is generally not a good idea. -- Wendy - 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: Reopen MPIR-180 (Repositories which require authentication get blacklisted)?
Please do not re-open issues that are marked as fixed in released versions, create a new issue and link back to the original one. Thanks, -Lukas Thierry Carre wrote: Hi all, My internal repository requires an authentication. When I build the Dependencies report with : mvn org.apache.maven.plugins:maven-project-info-reports-plugin:2.3:dependencies -- No problem, it works fine. but with : mvn org.apache.maven.plugins:maven-project-info-reports-plugin:2.3.1:dependencies -- my repository is blacklisted again, as with the older plugin versions ( 2.2) http://jira.codehaus.org/browse/MPIR-180 Am I alone in this case? (I'm using maven 3.0.2) Thanks Thierry -- View this message in context: http://maven.40175.n5.nabble.com/Reopen-MPIR-180-Repositories-which-require-authentication-get-blacklisted-tp4229472p4229472.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: Adding files to target before creating war
On Mon, Mar 21, 2011 at 11:28 AM, Sam Adams sbad...@gmail.com wrote: This is exactly what I'm trying to do. Why is this not a good idea and what are the alternatives? Depends on *why* you're trying to do that, which is why I asked what problem you're trying to solve. In general... either externalize the configuration or pack it all inside and use something that can select the right file so that you move the exact same war through the (I assume) different environments. If you build a war for QA, test it, and then build a war for production and deploy it... what have you *really* tested? -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding files to target before creating war
We have slightly different configurations that we need to test. For this very reason we need to build and test different profiles. This can include different web.xml files so I don't think externalising is an option in this case. Thanks, Sam On 21 March 2011 15:44, Wendy Smoak wsm...@gmail.com wrote: On Mon, Mar 21, 2011 at 11:28 AM, Sam Adams sbad...@gmail.com wrote: This is exactly what I'm trying to do. Why is this not a good idea and what are the alternatives? Depends on *why* you're trying to do that, which is why I asked what problem you're trying to solve. In general... either externalize the configuration or pack it all inside and use something that can select the right file so that you move the exact same war through the (I assume) different environments. If you build a war for QA, test it, and then build a war for production and deploy it... what have you *really* tested? -- Wendy - 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: Adding files to target before creating war
We have slightly different configurations that we need to test. For this very reason we need to build and test different profiles. This can include different web.xml files so I don't think externalising is an option in this case. If you pull in Spring or another DI framework, then you can probably make it work with some framework-specific configuration. The web.xml config would be identical across profiles but it would simply make a call out to some other loader that would pull in the details for the profile that you are trying to build/test. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: ZIP and UNZIP the code source in another project
On Mon, Mar 21, 2011 at 4:26 AM, Nguyen Tien Luong tienluon...@yahoo.com wrote: But does Overlay work in dev mode? It means when I modify some JSP in PROJECT-A, the PROJECT-B will be updated automatically at its deployment ( right click on PROJECT-B/ Run on server ) ? Maven doesn't have any right-click, it's a command line tool. :) You'd have to ask the developers of the IDE integration for whatever it is you're using. (And possibly open a bug, since you say it doesn't work.) -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven with ICEFACES
On Sun, Mar 20, 2011 at 3:59 PM, inforedaster inforedas...@gmail.com wrote: I just created a web project in myeclipse 8 and I use maven Support So I added JSF and ICEfaces capabilities in my project I put a You most likely need to ask the Icefaces guys and maybe even the MyEclipse folks about this. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Specific problem with Maven resources filtering
Hi everyone.
I'm using Maven to build my project and I'm stuck on the following problem:
I have a log4j.xml file with an appender configured like follows
appender name=audit-file
class=org.apache.log4j.DailyRollingFileAppender
param name=File
value=${jboss.server.log.dir}${file.separator}mte-imo-audit.log /
param name=DatePattern value='-'-MM-dd'.log' /
layout class=br.gov.dataprev.infra.audit.JsonLayout /
/appender
This file is being filtered by Maven to switch some other user custom
variables in other parts of the log4j.xml configuration (not shown above
because it´s not relevant to the problem), but I did not want Maven to
switch the value of ${file.separator}, which is intended to be a variable
for use of jboss. Unfortunately, as it is a variable that Maven recognizes,
it´s trying to change its value on 'mvn package' command. That´s a problem
to me, because I´m building the package using a machine that runs on Windows
and deploying in a machine that runs on Linux.
I know I could make profiles to try to fix this, but my first intention of
using ${file.separator} is to have a file that can be put on any OS and the
solution of using Maven profiles would make me rebuild the entire package
just to replace the file separator character.
So, I would like to know if there is a way to configure Maven in such a way
that after the Maven filtering, the final log4j.xml keeps the string
${file.separator} untouched, without having it switched for \ or /.
Thanks in advance and sorry for eventual grammar and vocabulary mistakes, as
English is not my first language. I hope I made myself clear enough.
Re: [ANN] Maven Findbugs plugin version 2.3.2 Released
Hm, the link points to 2.3.1, http://jira.codehaus.org/secure/ReleaseNote.jspa?version=16272projectId=11701 is for 2.3.2. Regards Mirko On Sun, Mar 20, 2011 at 23:52, Garvin LeClaire glecla...@insightbb.com wrote: Hi, The Mojo team is pleased to announce the release of the Maven FindBugs Plugin version 2.3.2. FindBugs uses static analysis to inspect Java bytecode for occurrences of bug patterns. You can see more about the plugin at: http://mojo.codehaus.org/findbugs-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdfindbugs-maven-plugin/artifactId version2.3.2/version /plugin Release Notes are at: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11701version=16025 Release Notes - Maven 2.x FindBugs Plugin - Version 2.3.2 ** Bug * [MFINDBUGS-109] - empty surefire report at the project site having findBugs in the reporting section * [MFINDBUGS-111] - Missing Bad Practice entries * [MFINDBUGS-112] - failOnError not being honored * [MFINDBUGS-113] - Inner classes are badly encoded in XML reports * [MFINDBUGS-122] - [Maven3] Could not find matching constructor for: org.codehaus.mojo.findbugs.FindbugsReportGenerator * [MFINDBUGS-126] - org.codehaus.mojo.findbugs.FindbugsReportGenerator(org.codehaus.doxia.module.xhtml.XhtmlSink * [MFINDBUGS-127] - Xref links are not generated with Maven 3 * [MFINDBUGS-128] - Empty classes in FindBugs report * [MFINDBUGS-132] - Findbugs doesn't run on projects containing only test classes * [MFINDBUGS-134] - Problems resolving pluginList ** Improvement * [MFINDBUGS-110] - Major performance degradation since FindBugs plugin 2.1 * [MFINDBUGS-119] - Update to GMaven 1.3 (to fix maven 3 build) * [MFINDBUGS-121] - The FindBugs documentation for parameters is verys sparse and should be improved * [MFINDBUGS-130] - Site doc pages refer to downlevel plugin version * [MFINDBUGS-133] - Add the ability to have multiple exclude filter files ** Wish * [MFINDBUGS-129] - maven3 Enjoy, The Mojo team. Garvin LeClaire glecla...@insightbb.com -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: redirecting source/javadoc
I'm pushing Apache Batik jars to maven. Batik uses an ant build. By using various ant patterns, it subdivides the source directory into 6 compiles and make 6 (different) jars. The ant build already sets up poms with dependencies, but whoever did all this did not make provisions for source and javadoc jars. In pushing their existing 1.7 release, I don't feel comfortable trying to do the level of surgery required to try to create accurate javadoc and source jars that correspond to the various jars. So, I can just punt on javadoc and sources if I have to. I had hoped that there was some trick whereby I could make them all point to a single javadoc and a single source artifact, but I read this thread as offering no joy of that sort. On Mon, Mar 21, 2011 at 1:39 AM, Anders Hammar and...@hammar.net wrote: No, there is no Maven way if doing this as the sources/javadoc jars are identifiied on their classifiers not by the POM. If it's in your repo manager, you should do some dirty workaround by using sym links in the background or similar. However, having a sources/javadoc containing more classes than the main jar could confuse people. If you are able to create 6 different jar, how come you can't create 6 different sources/javadoc jars? This might be a good time to do some refactoring of your build script. /Anders On Mon, Mar 21, 2011 at 03:38, Benson Margulies bimargul...@gmail.comwrote: Consider an ant build that creates 1/2-dozen jars from a single source hierarchy. It wants to be 6 maven artifacts. But there's no easy way to make six different jars of javadoc and sources. Is there any way for the poms of 5 to point to the sixth, or is it best to just post identical source/javadoc jars six times? - 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: Specific problem with Maven resources filtering
Hi
It seems that you need to escape filtering, which is possible. See
http://maven.apache.org/plugins/maven-resources-plugin/examples/escape-filtering.html
On 2011-03-21 20:54, Rafael Vanderlei wrote:
Hi everyone.
I'm using Maven to build my project and I'm stuck on the following problem:
I have a log4j.xml file with an appender configured like follows
appender name=audit-file
class=org.apache.log4j.DailyRollingFileAppender
param name=File
value=${jboss.server.log.dir}${file.separator}mte-imo-audit.log /
param name=DatePattern value='-'-MM-dd'.log' /
layout class=br.gov.dataprev.infra.audit.JsonLayout /
/appender
This file is being filtered by Maven to switch some other user custom
variables in other parts of the log4j.xml configuration (not shown above
because it´s not relevant to the problem), but I did not want Maven to
switch the value of ${file.separator}, which is intended to be a variable
for use of jboss. Unfortunately, as it is a variable that Maven recognizes,
it´s trying to change its value on 'mvn package' command. That´s a problem
to me, because I´m building the package using a machine that runs on Windows
and deploying in a machine that runs on Linux.
I know I could make profiles to try to fix this, but my first intention of
using ${file.separator} is to have a file that can be put on any OS and the
solution of using Maven profiles would make me rebuild the entire package
just to replace the file separator character.
So, I would like to know if there is a way to configure Maven in such a way
that after the Maven filtering, the final log4j.xml keeps the string
${file.separator} untouched, without having it switched for \ or /.
Thanks in advance and sorry for eventual grammar and vocabulary mistakes, as
English is not my first language. I hope I made myself clear enough.
--
Dennis Lundberg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Maven native:link naming exe
Hi All New to Maven and trying to figure out how I might use it for C++ projects on a windows platform. Downloaded Maven 3.0.2 and trying to use the Native Maven plugin. Using compiler provider msvc and compilerExecutable as cl I have been able to get source compiled. However when I try to link it seem to be using the wrong cl option i.e. /out rather than /Fe. I get the following type of output: [INFO] --- native-maven-plugin:1.0-alpha-7:link (default-cli) @ my-cpp-app --- [INFO] cmd.exe /X /C cl /out:c:\Users\Steve\my-cpp-app\target\my-cpp-app-1.0-SNAPSHOT.exe target\objs\HelloWorldApp.obj Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.21022.08 for 80x86 Copyright (C) Microsoft Corporation. All rights reserved. cl : Command line warning D9035 : option 'o' has been deprecated and will be removed in a future release Microsoft (R) Incremental Linker Version 9.00.21022.08 Copyright (C) Microsoft Corporation. All rights reserved. /out:HelloWorldApp.exe /out:ut:c:\Users\Steve\my-cpp-app\target\my-cpp-app-1.0-SNAPSHOT.exe target\objs\HelloWorldApp.obj LINK : fatal error LNK1104: cannot open file 'ut:c:\Users\Steve\my-cpp-app\target\my-cpp-app-1.0-SNAPSHOT.exe' Thanks in advance Steve -- View this message in context: http://maven.40175.n5.nabble.com/Maven-native-link-naming-exe-tp4239754p4239754.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven with ICEFACES
You probably don't need to include JSF as part of your WAR file? It looks like there's a conflict between versions of JSF (the version provided by the container, and the version provided by your WAR file?). If this is the case, change the scope in Maven for the JSF dependencies to provided. If you want to use a later version of JSF, you should patch the container not provide the jars in the WAR file. That's been my experience with Glassfish, anyways. I can't speak for other app containers, though, having never used them in anger. Hope this helps, Ed On Mon, Mar 21, 2011 at 6:59 AM, inforedaster inforedas...@gmail.comwrote: I just created a web project in myeclipse 8 and I use maven Support So I added JSF and ICEfaces capabilities in my project I put a single home page in the project but when I deployed the project in of myeclipse tomcat (I tried the same thing by installing Tomcat7) when I start the server it gives me errors I have not understood or it come!! is that you have a proposal about?! Error : 19 mars 2011 11:13:32 org.apache.catalina.core.AprLifecycleListener init INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Common Files\MyEclipse\binary\com.sun.java.jdk.win32.x86_1.6.0.013\bin;C:\Program Files\Common Files\MyEclipse\plugins\com.genuitec.eclipse.easie.tomcat.myeclipse_8.6.0.me201007231647\tomcat\bin 19 mars 2011 11:13:32 org.apache.coyote.http11.Http11Protocol init INFO: Initialisation de Coyote HTTP/1.1 sur http-8080 19 mars 2011 11:13:32 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 798 ms 19 mars 2011 11:13:32 org.apache.catalina.core.StandardService start INFO: Démarrage du service Catalina 19 mars 2011 11:13:32 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.13 19 mars 2011 11:13:34 com.sun.faces.config.ConfigureListener contextInitialized INFO: Initializing Sun's JavaServer Faces implementation (1.2_04-b07-FCS) for context '/criam-web' 19 mars 2011 11:13:34 com.icesoft.faces.application.ViewRootStateManagerImpl INFO: ViewRootStateManagerImpl constructed with Delegate: com.sun.faces.application.StateManagerImpl@1ba0f36 19 mars 2011 11:13:34 com.icesoft.faces.application.D2DViewHandler INFO: ICEsoft Technologies, Inc. ICEfaces 1.8.1 Build number: 7 Revision: 18926 19 mars 2011 11:13:35 org.apache.catalina.core.StandardContext listenerStart GRAVE: Exception lors de l'envoi de l'évènement contexte initialisé (context initialized) à l'instance de classe d'écoute (listener) com.sun.faces.config.ConfigureListener java.lang.LinkageError: loader constraint violation: when resolving interface method javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory; the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, com/sun/faces/config/ConfigureListener, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ExpressionFactory used in the signature at com.sun.faces.config.ConfigureListener.registerELResolverAndListenerWithJsp(ConfigureListener.java:1628) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:453) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:566) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
Re: Maven native:link naming exe
do you have chance to take a look at existing examples? If the examples dont work out for you, perhaps a pom file will help to figure out the issue -D On Mon, Mar 21, 2011 at 2:00 PM, stevek st...@dsoft-solutions.co.uk wrote: Hi All New to Maven and trying to figure out how I might use it for C++ projects on a windows platform. Downloaded Maven 3.0.2 and trying to use the Native Maven plugin. Using compiler provider msvc and compilerExecutable as cl I have been able to get source compiled. However when I try to link it seem to be using the wrong cl option i.e. /out rather than /Fe. I get the following type of output: [INFO] --- native-maven-plugin:1.0-alpha-7:link (default-cli) @ my-cpp-app --- [INFO] cmd.exe /X /C cl /out:c:\Users\Steve\my-cpp-app\target\my-cpp-app-1.0-SNAPSHOT.exe target\objs\HelloWorldApp.obj Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.21022.08 for 80x86 Copyright (C) Microsoft Corporation. All rights reserved. cl : Command line warning D9035 : option 'o' has been deprecated and will be removed in a future release Microsoft (R) Incremental Linker Version 9.00.21022.08 Copyright (C) Microsoft Corporation. All rights reserved. /out:HelloWorldApp.exe /out:ut:c:\Users\Steve\my-cpp-app\target\my-cpp-app-1.0-SNAPSHOT.exe target\objs\HelloWorldApp.obj LINK : fatal error LNK1104: cannot open file 'ut:c:\Users\Steve\my-cpp-app\target\my-cpp-app-1.0-SNAPSHOT.exe' Thanks in advance Steve -- View this message in context: http://maven.40175.n5.nabble.com/Maven-native-link-naming-exe-tp4239754p4239754.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: Maven native:link naming exe
Do you recommend a particular example or examples. Could you point me to these please. Steve - Original Message - From: Dan Tran [via Maven] To: stevek Sent: Monday, March 21, 2011 10:10 PM Subject: Re: Maven native:link naming exe do you have chance to take a look at existing examples? If the examples dont work out for you, perhaps a pom file will help to figure out the issue -D On Mon, Mar 21, 2011 at 2:00 PM, stevek [hidden email] wrote: Hi All New to Maven and trying to figure out how I might use it for C++ projects on a windows platform. Downloaded Maven 3.0.2 and trying to use the Native Maven plugin. Using compiler provider msvc and compilerExecutable as cl I have been able to get source compiled. However when I try to link it seem to be using the wrong cl option i.e. /out rather than /Fe. I get the following type of output: [INFO] --- native-maven-plugin:1.0-alpha-7:link (default-cli) @ my-cpp-app --- [INFO] cmd.exe /X /C cl /out:c:\Users\Steve\my-cpp-app\target\my-cpp-app-1.0-SNAPSHOT.exe target\objs\HelloWorldApp.obj Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.21022.08 for 80x86 Copyright (C) Microsoft Corporation. All rights reserved. cl : Command line warning D9035 : option 'o' has been deprecated and will be removed in a future release Microsoft (R) Incremental Linker Version 9.00.21022.08 Copyright (C) Microsoft Corporation. All rights reserved. /out:HelloWorldApp.exe /out:ut:c:\Users\Steve\my-cpp-app\target\my-cpp-app-1.0-SNAPSHOT.exe target\objs\HelloWorldApp.obj LINK : fatal error LNK1104: cannot open file 'ut:c:\Users\Steve\my-cpp-app\target\my-cpp-app-1.0-SNAPSHOT.exe' Thanks in advance Steve -- View this message in context: http://maven.40175.n5.nabble.com/Maven-native-link-naming-exe-tp4239754p4239754.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] - To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] -- If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Maven-native-link-naming-exe-tp4239754p4241740.html To unsubscribe from Maven native:link naming exe, click here. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-native-link-naming-exe-tp4239754p4243013.html Sent from the Maven - Users mailing list archive at Nabble.com.
simple branching won't work
Hello, I followed the instructions here: http://maven.apache.org/guides/mini/guide-releasing.html So my input pom.xml looks like shown below. Executing: mvn release:branch -DbranchName=4.0 gets me to the FAILED ouput also shown below. Why is it always trying to create a branches folder when the pom.xml clearly says tags !? Why is it not building the war and putting it into the local repo? I have spent two days on this ... every other online documentation would have a completely different idea on how SCM should be configured ... Can anyone please advice. TIA, regards, Giovanni ** pom.xml ** project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdwebengineering/groupId artifactIdfacebookapp/artifactId packagingwar/packaging version4.0-SNAPSHOT/version namefacebookapp Maven Webapp/name urlhttp://maven.apache.org/url dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency dependency groupIdcom.restfb/groupId artifactIdrestfb/artifactId version1.6.2/version /dependency dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-servlet_2.5_spec/artifactId version1.2/version /dependency /dependencies inceptionYear2011/inceptionYear licenses license nameGNU Lesser General Public License/name urlCOPYING.LESSER/url /license license nameGNU General Public License/name urlCOPYING/url /license /licenses scm connectionscm:svn:https://svn.vis.ethz.ch/svn/webengineering/trunk/connection developerConnectionscm:svn:file:///Users/bravegag/code/webengineering/trunk/developerConnection urlhttp://svn.vis.ethz.ch/svn/webengineering/trunk/url /scm build finalNamefacebookapp/finalName plugins plugin artifactIdmaven-release-plugin/artifactId configuration tagBasefile:///Users/bravegag/code/webengineering/tags/tagBase /configuration /plugin plugin groupIdorg.mortbay.jetty/groupId artifactIdjetty-maven-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId inheritedtrue/inherited configuration wtpversion1.5/wtpversion classpathContainers classpathContainerorg.eclipse.jdt.launching.JRE_CONTAINER/classpathContainer classpathContainerorg.eclipse.jdt.USER_LIBRARY/TOMCAT_7.0.8_LIBRARY/classpathContainer /classpathContainers /configuration /plugin /plugins /build /project ** OUTPUT ** /Users/bravegag/code/webengineering/trunk$ mvn release:branch -DbranchName=4.0 [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for webengineering:facebookapp:war:4.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.mortbay.jetty:jetty-maven-plugin is missing. @ line 85, column 15 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-eclipse-plugin is missing. @ line 89, column 15 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] [INFO] Building facebookapp Maven Webapp 4.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-release-plugin:2.0:branch (default-cli) @ facebookapp --- [INFO] Verifying that there are no local modifications... [INFO] Executing: /bin/sh -c cd /Users/bravegag/code/webengineering/trunk svn --non-interactive status [INFO] Working directory: /Users/bravegag/code/webengineering/trunk What is the new working copy version for facebookapp Maven Webapp? (webengineering:facebookapp) 4.1-SNAPSHOT: : 5.0 [INFO] Transforming 'facebookapp Maven Webapp'... [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/bravegag/code/webengineering/trunk svn --non-interactive commit --file /var/folders/5m/5mC0wYCSGMK8NbPZYhBEZE+++TI/-Tmp-/maven-scm-1430166965.commit --targets
Re: redirecting source/javadoc
On Tue, Mar 22, 2011 at 7:12 AM, Benson Margulies bimargul...@gmail.com wrote: I'm pushing Apache Batik jars to maven. Batik uses an ant build. By using various ant patterns, it subdivides the source directory into 6 compiles and make 6 (different) jars. The ant build already sets up poms with dependencies, but whoever did all this did not make provisions for source and javadoc jars. In pushing their existing 1.7 release, I don't feel comfortable trying to do the level of surgery required to try to create accurate javadoc and source jars that correspond to the various jars. So, I can just punt on javadoc and sources if I have to. I had hoped that there was some trick whereby I could make them all point to a single javadoc and a single source artifact, but I read this thread as offering no joy of that sort. Not in Maven directly. The best way would be to convince them to move to Maven and have it fixed for free :) In the meantime, you can hack your ant scripts to generate the source and javadoc. It sounds like you already have the 6 patterns since the jars are generated from these. The poms you use for these project's aren't real poms (since you aren't building your project's with them). The poms are like stubs so that maven projects can pull down Batik jars. So they don't need buildplugin sections to drive generating source/javadoc jars. They just need to make sure their dependency sections are correct. Then you need to get your pom, artifact.jar, source.jar, javadoc.jar uploaded into central and everything is done. Does this make sense? Barrie - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven native:link naming exe
which example(s) are you having problem with? they are under native-maven-plugin/src/it It seems you are using msvc 2008, did you configure the correct factory? -Dan On Mon, Mar 21, 2011 at 4:01 PM, stevek st...@dsoft-solutions.co.uk wrote: Do you recommend a particular example or examples. Could you point me to these please. Steve - Original Message - From: Dan Tran [via Maven] To: stevek Sent: Monday, March 21, 2011 10:10 PM Subject: Re: Maven native:link naming exe do you have chance to take a look at existing examples? If the examples dont work out for you, perhaps a pom file will help to figure out the issue -D On Mon, Mar 21, 2011 at 2:00 PM, stevek [hidden email] wrote: Hi All New to Maven and trying to figure out how I might use it for C++ projects on a windows platform. Downloaded Maven 3.0.2 and trying to use the Native Maven plugin. Using compiler provider msvc and compilerExecutable as cl I have been able to get source compiled. However when I try to link it seem to be using the wrong cl option i.e. /out rather than /Fe. I get the following type of output: [INFO] --- native-maven-plugin:1.0-alpha-7:link (default-cli) @ my-cpp-app --- [INFO] cmd.exe /X /C cl /out:c:\Users\Steve\my-cpp-app\target\my-cpp-app-1.0-SNAPSHOT.exe target\objs\HelloWorldApp.obj Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.21022.08 for 80x86 Copyright (C) Microsoft Corporation. All rights reserved. cl : Command line warning D9035 : option 'o' has been deprecated and will be removed in a future release Microsoft (R) Incremental Linker Version 9.00.21022.08 Copyright (C) Microsoft Corporation. All rights reserved. /out:HelloWorldApp.exe /out:ut:c:\Users\Steve\my-cpp-app\target\my-cpp-app-1.0-SNAPSHOT.exe target\objs\HelloWorldApp.obj LINK : fatal error LNK1104: cannot open file 'ut:c:\Users\Steve\my-cpp-app\target\my-cpp-app-1.0-SNAPSHOT.exe' Thanks in advance Steve -- View this message in context: http://maven.40175.n5.nabble.com/Maven-native-link-naming-exe-tp4239754p4239754.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] - To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] -- If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Maven-native-link-naming-exe-tp4239754p4241740.html To unsubscribe from Maven native:link naming exe, click here. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-native-link-naming-exe-tp4239754p4243013.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
dependency conflict issue ( dummy commons logging libs/repo )
I am not sure a lower version dependency seems to be trumping a higher version. Here is the POM http://pastebin.com/TBP0YTZs Here is the dependency tree http://pastebin.com/VBdjiVcL Whats going on here ? I was attempting to avoid transitive dependency of commons-logging. I followed the repo here that hosts a dummy library with very large version number ( 99.0... ) to do so. http://www.slf4j.org/faq.html#excludingJCL specifically the pom config from this file. http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-not-exist.html But for some reason commons-logging version:1.1.1 seems to trump out version:99.0-does-not-exist thanks Arun
