Packaging EE applications (Real problem!!!!)
Hi! I'm trying to make a real world ear. I've 2 wars with lot of dependencies. Some of them are shared. What I'm trying to do is not to include the libraries in my wars (I've resolved it by adding the addClasspath clause in my manifest configuration) but include them in the ear. There is some information about this there... http://jira.codehaus.org/browse/MWAR-21 http://jira.codehaus.org/browse/MWAR-9 http://jira.codehaus.org/browse/MEAR-17 As a workaround, I've copied all the wars dependencies into the ear pom.xml, but, I know, It's horrible! :) Is there a better solution??? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependency problem with hibernate-annotations
très bien! I've already done that. At the moment, I've no problem. I only wanted to warn it just in case it's a mistake. Perhaps the mantainer could see it. thanks very much! Sebastien Cesbron wrote: You have to install it by hand on your own repository. The package is not available on public repositories. I don't know if this is a license related problem or just because it is in beta On 7/27/06, German de la Cruz [EMAIL PROTECTED] wrote: Hi people, org.hibernate.hibernate-annotations.3.2.0.cr1 depends on dependency groupIdjavax.persistence/groupId artifactIdejb/artifactId version3.0-public-draft-20060502/version /dependency Which actually doesn't exist in maven2 repository. Is there a resposible to fix it? Thanks! German,. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
dependency problem with hibernate-annotations
Hi people, org.hibernate.hibernate-annotations.3.2.0.cr1 depends on dependency groupIdjavax.persistence/groupId artifactIdejb/artifactId version3.0-public-draft-20060502/version /dependency Which actually doesn't exist in maven2 repository. Is there a resposible to fix it? Thanks! German,. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Wagon, WebDAV and HTTP Proxy
Hi people, Last night, I configured my deploys with webDAV wagon. Everything worked perfect. But, now in my office and behind a http proxy, I can't get connected to my server. I've no problems downloadings any library or plugin from Internet, because I've configured in my settings.xml my http proxy. It seems WebDAV wagon doesn't use this settings. is there any way to deploy in my server behind a firewall?? Thanks! German.- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven scm with subversion: Cannot copy path '.' into its own child '../tags/0_1'
thanks julian for your replying... if I make svn copy . ../tags/tapestry4-playroom-0_1 I obtain the same error, but if I make... svn copy -m comment... https://localhost/svn/repos/tapestry4-playroom/trunk https://localhost/svn/repos/tags/0_1 I works perfectly tapestry4-playroom is a svn working copy, I checkout it with eclipse. I try without the tag directory and, after that, creating it first. No way. Yesterday, I try using mvn release:prepare from another machine, and I works!! Then, It can't be a problem in the server I think Searching in google, I've found some pages with people with the same problem, like this: http://mail-archives.apache.org/mod_mbox/maven-users/200512.mbox/[EMAIL PROTECTED] It's very strange, isn't it? Thanks On 2/8/06, Julian Wood [EMAIL PROTECTED] wrote: It looks right to me. Did you delete the release.properties file and try again? tapestry4-playroom is an svn working copy? The tags directory exists in your svn repo? Maven is trying to copy everything in trunk to tags/tapestry4- playroom-0_1. So try on the command line (there should be a trunk and tags directory locally and in the svn repo below the tapestry4- playroom dir) : tapestry4-playroom $ svn copy trunk tags/tapestry4-playroom-0_1 tapestry4-playroom $ svn commit -m Released version 0_1 Get it working there first, and it should work with maven. J On 8-Feb-06, at 2:29 PM, German de la Cruz wrote: After some hours of trial an error, I wasn't able to make scm with subversion work svn: Cannot copy path '.' into its own child '../tags/0_1' Every time I run maven release:prepare, I obtain the next error I'm running it in linux Thanks guys! [DEBUG] Configuring mojo ' org.apache.maven.plugins:maven-release-plugin:2.0-beta-3:prepare' -- [DEBUG] (f) basedir = /home/gdelacruz/develop/workspace/tapestry4- playroom [DEBUG] (f) generateReleasePoms = false [DEBUG] (f) interactive = true [DEBUG] (f) localRepository = [local] - file:///home/gdelacruz/.m2/repository [DEBUG] (f) password = [DEBUG] (f) reactorProjects = [ [EMAIL PROTECTED] [DEBUG] (f) resume = false [DEBUG] (f) settings = [EMAIL PROTECTED] [DEBUG] (f) tagBase = https://localhost/svn/repos/tapestry4- playroom/tags [DEBUG] (f) urlScm = scm:svn: https://localhost/svn/repos/tapestry4-playroom/trunk [DEBUG] (f) username = ger [DEBUG] -- end configuration -- [INFO] [release:prepare] [INFO] Verifying there are no local modifications ... [INFO] Checking lineage for snapshots ... [INFO] Checking dependencies for snapshots ... [INFO] Checking plugins for snapshots ... [INFO] What is the release version for 'tests:tapestry4-playroom'? [0.1] 0_1 [INFO] What tag name should be used? 0_1 [INFO] Checking in modified POMs [INFO] Tagging release with the label 0_1. Provider message: The svn tag command failed. Command output: svn: No se puede copiar la ruta '.' a su propio descendiente '../ tags/0_1' (it means svn: Cannot copy path '.' into its own child '../tags/0_1' [INFO] -- -- [ERROR] BUILD ERROR [INFO] -- -- [INFO] An error is occurred in the tag process. Embedded error: Error! [INFO] -- -- [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in the tag process. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneG oal( DefaultLifecycleExecutor.java:485) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:455) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand leFailures (DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment s( DefaultLifecycleExecutor.java:216) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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:585) at org.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java :315
maven scm with subversion: Cannot copy path '.' into its own child '../tags/0_1'
After some hours of trial an error, I wasn't able to make scm with subversion work svn: Cannot copy path '.' into its own child '../tags/0_1' Every time I run maven release:prepare, I obtain the next error I'm running it in linux Thanks guys! [DEBUG] Configuring mojo ' org.apache.maven.plugins:maven-release-plugin:2.0-beta-3:prepare' -- [DEBUG] (f) basedir = /home/gdelacruz/develop/workspace/tapestry4-playroom [DEBUG] (f) generateReleasePoms = false [DEBUG] (f) interactive = true [DEBUG] (f) localRepository = [local] - file:///home/gdelacruz/.m2/repository [DEBUG] (f) password = [DEBUG] (f) reactorProjects = [ [EMAIL PROTECTED] [DEBUG] (f) resume = false [DEBUG] (f) settings = [EMAIL PROTECTED] [DEBUG] (f) tagBase = https://localhost/svn/repos/tapestry4-playroom/tags [DEBUG] (f) urlScm = scm:svn: https://localhost/svn/repos/tapestry4-playroom/trunk [DEBUG] (f) username = ger [DEBUG] -- end configuration -- [INFO] [release:prepare] [INFO] Verifying there are no local modifications ... [INFO] Checking lineage for snapshots ... [INFO] Checking dependencies for snapshots ... [INFO] Checking plugins for snapshots ... [INFO] What is the release version for 'tests:tapestry4-playroom'? [0.1] 0_1 [INFO] What tag name should be used? 0_1 [INFO] Checking in modified POMs [INFO] Tagging release with the label 0_1. Provider message: The svn tag command failed. Command output: svn: No se puede copiar la ruta '.' a su propio descendiente '../tags/0_1' (it means svn: Cannot copy path '.' into its own child '../tags/0_1' [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error is occurred in the tag process. Embedded error: Error! [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in the tag process. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal( DefaultLifecycleExecutor.java:485) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:455) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:216) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java :315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java :430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred in the tag process. at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease( PrepareReleaseMojo.java:1414) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute( PrepareReleaseMojo.java:246) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:531) ... 16 more Caused by: org.apache.maven.scm.ScmException: Error! at org.apache.maven.plugins.release.helpers.ScmHelper.checkResult( ScmHelper.java:124) at org.apache.maven.plugins.release.helpers.ScmHelper.tag( ScmHelper.java:226) at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease( PrepareReleaseMojo.java:1410) ... 19 more [INFO] [INFO] Total time: 10 seconds [INFO] Finished at: Wed Feb 08 17:59:22 ART 2006 [INFO] Final Memory: 4M/8M [INFO] My pom... ?xml version=1.0 encoding=UTF-8?project modelVersion4.0.0/modelVersion groupIdtests/groupId artifactIdtapestry4-playroom/artifactId nameMaven Quick Start Archetype/name version0.1-SNAPSHOT/version descriptiontapestry4-playroom/description
best place to put the username??
Hi people, I'm very new to maven 2, but I've been a maven 1.0 user for a time. I've read all the theory about profiles, which brings to me a question: What is the best place to put my username and password for the maven-scm-plugin. Perhaps the pom.xml is not the best place (In the plugin configuration) because, for security reasons, each developer might have his own user. Then, I think of configuring this plugin in the settings.xml. but I can't :( Then it think of creating a profile (named default), mark it as the activeProfile and then define a property called username. Finally in the plugin configuration, use the property. What do you think? It's a bit twisted, isn't it? Hoping from hearing from you soon Best Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
