Re: Resource filtering difficulties.
Thanks! On Sat, Jan 9, 2010 at 5:36 PM, Olivier Lamy ol...@apache.org wrote: Hi, You can try with configuring the resources mojo as this : useDefaultDelimitersfalse/useDefaultDelimiters delimiters delimiter${*}/delimiter /delimiters The @ won't be use as delimiter. -- Olivier 2010/1/8 Karel Vervaeke ka...@outerthought.org: I'm having difficulties with resource filtering In my pom I have: resource targetPathsome path/targetPath filteringtrue/filtering directory${basedir}/src/main/xpatch/directory includesinclude*/include/includes /resource plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId configuration escapeString\/escapeString /configuration /plugin in src/main/xpatch I have: ?xml version=1.0? patches xmlns:map=http://apache.org/cocoon/sitemap/1.0; patch xpath=/runtime/containers remove=artifa...@id='competent']/ patch xpath=/runtime/containers remove=artifa...@id='doctasks']/ patch xpath=/runtime/containers insert-after=artifa...@id='workflow'] artifact id=doctasks groupId=daisy artifactId=daisy-doctaskrunner-server-impl version=${myversion}/ artifact id=doctasks groupId=daisy artifactId=daisy-doctaskrunner-server-impl version=${myversion} / artifact id=workflow groupId=daisy artifactId=daisy-workflow-server-impl version=${myversion}/ /patch /patches In the output, ${myversion} is not replaced. I have determined that the problem is caused by the fact that the @ is also a I have also tried escaping the @ using the escape string defined in the pom, but then the output looks like this:: patch xpath=/runtime/containers remove=artifa...@id='competent']/ patch xpath=/runtime/containers remove=artifac...@id='doctasks']/ patch xpath=/runtime/containers insert-after=artifac...@id='workflow'] ... (The first \@ is escaped, but for the others nothing happens. IIUC this has to do with the fact that the escape string is used to escape pairs of at signs, but that seems like a strange way to handle things). I found some more info here: http://maven.apache.org/shared/maven-filtering/, but nothing that helped In the end I ended up defining a property at=@ and using ${at} in my resource, which works but isn't very nice. Does anyone have ideas about this? Regards, Karel0 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier - 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
How to add proxy information to Wagon Manager that comes from the plexus container?
Hi All, (Sorry for unrelated post on this list, but I tried on plexus and wagon user list and got no response so this is just hit and try for me, thanks if someone can help..) I am creating an application using plexus container and in need of adding proxy information to wagon manager,Right now I am adding proxy this way : NOTE : pc is plexus container DefaultWagonManager dwm; try { dwm = (DefaultWagonManager)pc.lookup(WagonManager.ROLE); dwm.addProxy(http,www-myhost.com,80,null,null,null); } catch (ComponentLookupException e) { } // And this way everything works fine, but wondering . is it the right way to add proxy info to Wagon manager? Is it possible that lookup will not always return me the Wagon manager? Thanks, Amaresh
Re: How to add proxy information to Wagon Manager that comes from the plexus container?
this may help http://svn.codehaus.org/mojo/tags/wagon-maven-plugin-1.0-beta-2/src/main/java/org/codehaus/mojo/wagon/shared/WagonUtils.java -D On Mon, Jan 11, 2010 at 1:46 AM, amaresh mourya amaresh.mou...@gmail.com wrote: Hi All, (Sorry for unrelated post on this list, but I tried on plexus and wagon user list and got no response so this is just hit and try for me, thanks if someone can help..) I am creating an application using plexus container and in need of adding proxy information to wagon manager,Right now I am adding proxy this way : NOTE : pc is plexus container DefaultWagonManager dwm; try { dwm = (DefaultWagonManager)pc.lookup(WagonManager.ROLE); dwm.addProxy(http,www-myhost.com,80,null,null,null); } catch (ComponentLookupException e) { } // And this way everything works fine, but wondering . is it the right way to add proxy info to Wagon manager? Is it possible that lookup will not always return me the Wagon manager? Thanks, Amaresh - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
m2eclipse plugin does not resolve properties from settings.xml
Hi there, We are using m2eclipse plugin for our maven2 project in eclipse. It seems it cannot resolve properties from settings file. When we enabled Dependency Management for M2 plugin it gives errors for the main pom.xml that cannot resolve systempath for the dependencies in system scope. Here is the errors Eclipse produces when enabled dependency management of M2 plugin: - Project build error: For dependency weblogic:weblogic:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/weblogic.jar - Project build error: For dependency weblogic:webservices:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/webservices.jar - Project build error: For dependency weblogic:jms510:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/jms510.jar - Project build error: For dependency weblogic:wlsybase:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/wlsybase.jar - Project build error: For dependency javax.net.ssl:jsse:jar: system-scoped dependency must specify an absolute systemPath but is ${java1_4.home}/jre/lib/jsse.jar The dependencies defined in the main pom.xml as follows: dependency groupIdweblogic/groupId artifactIdweblogic/artifactId version8.1.4.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/weblogic.jar/systemPath /dependency dependency groupIdweblogic/groupId artifactIdwebservices/artifactId version1.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/webservices.jar/systemPath /dependency dependency groupIdweblogic/groupId artifactIdwlsybase/artifactId version1.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/wlsybase.jar/systemPath /dependency dependency groupIdweblogic/groupId artifactIdjms510/artifactId version8.1.4.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/jms510.jar/systemPath /dependency dependency groupIdjavax.net.ssl/groupId artifactIdjsse/artifactId version1.4.2/version scopesystem/scope systemPath${java1_4.home}/jre/lib/jsse.jar/systemPath /dependency Properties are defined in profile in settings.xml and the profile activated. The project builds when we run it through command line or eclipse without enabling dependency management of M2 plugin. Any help on this would be greatly appreceated. Regards Maruf - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
missing artifact: tools.jar 1.5.0
I am using the following tools: - Windows XP sp3 - Eclipse Galileo 3.5.1 - installed at C:\eclipse with eclipse.ini configured to point to my JDK, not JRE. - Maven 2.2.1 - installed at C:\apache-maven-2.2.1 - MySQL - installed at C:\Program Files\MySQL\MySQL Server 5.1 - JDK 1.6.17 - installed at C:\SDKs - JAVA_HOME system environment variable is pointing my JDK installation. - PATH system environment variable includes paths to JAVA_HOME, MAVEN_HOME, and MYSQL_HOME which all point to their respective installations. When I run the command, *mvn eclipse:eclipse*, I receive the following error: C:\workspace\almmmvn eclipse:eclipse [INFO] Scanning for projects... [INFO] [INFO] Building AppFuse Struts 2 Application [INFO]task-segment: [eclipse:eclipse] [INFO] [INFO] Preparing eclipse:eclipse [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) com.sun:tools:jar:1.5.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun -DartifactId=tools -Dversion=1. 5.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun -DartifactId=tools -Dversion=1.5. 0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) xxx.xx.::war:1.0-SNAPSHOT 2) org.apache.struts:struts2-core:jar:2.1.8 3) com.sun:tools:jar:1.5.0 -- 1 required artifact is missing. for artifact: xxx.xx.::war:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), appfuse-snapshots ( http://oss.sonatype.org/content/repositories/appfuse-snapsh ots) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Sun Jan 10 16:52:49 EST 2010 [INFO] Final Memory: 21M/38M [INFO] So I run the command, *mvn install:install-file -DgroupId=com.sun -DartifactId=tools -Dversion=1.5.0 -Dpackaging=jar -Dfile=C:\SDKs\lib\tools.jar*, to install the tools.jar and I verify that it exists in the correct location. Then I run the command, *mvn eclipse:eclipse*, again and it still fails with the same error. I checked a lot of the documentation online and the solutions say to ensure that Eclipse is being run using a JDK, not a JRE. I believe I ensured this with the -vm arguments that I included in my eclipse.ini file. But this issue is occuring when I run the *mvn eclipse:eclipse* from the command prompt. Any ideas? Thank you, Rachel
windows 7- build error - on install
I get the following error when tying to install Maven on Windows 7 I have Java installed and am now trying to install Maven. C:\Users\user\Documents\apache-maven-2.2.1\binmvn clean install [INFO] Scanning for projects... [INFO] [INFO] Building Maven Default Project [INFO] task-segment: [clean, install] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot execute mojo: clean. It requires a project with an existing pom.xml, but the build is not using one. [INFO] How can I resolve this error? Where should the pom.xml file be located? Should the pom.xml be generated on the binary extraction or during the install? thanks, Ed
Re: windows 7- build error - on install
I suggest you read this to get started with Maven: http://www.sonatype.com/books/mvnex-book/reference/public-book.html /Anders On Sun, Jan 10, 2010 at 17:28, edward cook ecook0...@yahoo.com wrote: I get the following error when tying to install Maven on Windows 7 I have Java installed and am now trying to install Maven. C:\Users\user\Documents\apache-maven-2.2.1\binmvn clean install [INFO] Scanning for projects... [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [clean, install] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot execute mojo: clean. It requires a project with an existing pom.xml, but the build is not using one. [INFO] How can I resolve this error? Where should the pom.xml file be located? Should the pom.xml be generated on the binary extraction or during the install? thanks, Ed
eroor in executin compile on hibernate project.
Hi there; I am trying to execute clean and install goals on hinernate project; And My out put is as given below. Will you please describe the sitution why this error is coming? I am not able to find any relevent answer till now. In eclispe this project is working well without any error. So i think this is something with meven compiler. But not aware of What? will you please describe the reason for me? Also added the error file. +===++ D:\VijayAtWork\TeamProjects\accounts-trunk\accountsmvn -e clean package + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building accounts [INFO]task-segment: [clean, package] [INFO] [INFO] [clean:clean] [INFO] Deleting directory D:\VijayAtWork\TeamProjects\accounts-trunk\accounts\target [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [WARNING] While downloading aspectj:aspectjweaver:1.5.4 This artifact has been relocated to org.aspectj:aspectjweaver:1.5.4. [WARNING] While downloading javax.xml.soap:saaj-impl:1.3 This artifact has been relocated to com.sun.xml.messaging.saaj:saaj-impl:1.3. Downloading: http://192.168.1.200:8014/artifactory/repo/org/springframework/spring-hibernate3/2.0-rc2/spring-hibernate3-2.0-rc2.pom Downloading: http://192.168.1.200:8014/artifactory/repo/woodstox/wstx-asl/3.2.7/wstx-asl-3.2.7.pom [INFO] [compiler:compile] [INFO] Compiling 1267 source files to D:\VijayAtWork\TeamProjects\accounts-trunk\accounts\target\classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure D:\VijayAtWork\TeamProjects\accounts-trunk\accounts\src\main\java\com\vsd\accounts\model\hibernate\package-info.java:[92,0] illegal start of expression D:\VijayAtWork\TeamProjects\accounts-trunk\accounts\src\main\java\com\vsd\accounts\model\hibernate\package-info.java:[92,0] illegal start of expression [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Compilation failure D:\VijayAtWork\TeamProjects\accounts-trunk\accounts\src\main\java\com\vsd\accounts\model\hibernate\package-info.java:[92,0] illegal start of expression at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.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.CompilationFailureException: Compilation failure D:\VijayAtWork\TeamProjects\accounts-trunk\accounts\src\main\java\com\vsd\accounts\model\hibernate\package-info.java:[92,0] illegal start of expression at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) ... 16 more [INFO] [INFO] Total time: 24 seconds [INFO] Finished at: Mon Jan 11 18:26:15 IST 2010 [INFO] Final Memory: 15M/254M [INFO] D:\VijayAtWork\TeamProjects\accounts-trunk\accounts
RE: m2eclipse plugin does not resolve properties from settings.xml
Any help on this would be greatly appreceated. Something to try - have you done a mvn install from the CLI for it (you mention the build works, but not which goal, so thought I would mention it)? A few times I've had unexplainable build problems when first setting up a new Eclipse workspace with an existing product. After a mvn install, things are magically better. And you are using the dev version of m2eclipse? If not, you should - it's more stable than the official release. -Original Message- From: Maruf Aytekin [mailto:aayte...@gmail.com] Sent: Monday, January 11, 2010 5:59 AM To: users@maven.apache.org Subject: m2eclipse plugin does not resolve properties from settings.xml Hi there, We are using m2eclipse plugin for our maven2 project in eclipse. It seems it cannot resolve properties from settings file. When we enabled Dependency Management for M2 plugin it gives errors for the main pom.xml that cannot resolve systempath for the dependencies in system scope. Here is the errors Eclipse produces when enabled dependency management of M2 plugin: - Project build error: For dependency weblogic:weblogic:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/weblogic.jar - Project build error: For dependency weblogic:webservices:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/webservices.jar - Project build error: For dependency weblogic:jms510:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/jms510.jar - Project build error: For dependency weblogic:wlsybase:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/wlsybase.jar - Project build error: For dependency javax.net.ssl:jsse:jar: system-scoped dependency must specify an absolute systemPath but is ${java1_4.home}/jre/lib/jsse.jar The dependencies defined in the main pom.xml as follows: dependency groupIdweblogic/groupId artifactIdweblogic/artifactId version8.1.4.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/weblogic.jar/systemPath /dependency dependency groupIdweblogic/groupId artifactIdwebservices/artifactId version1.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/webservices.jar/systemPath /dependency dependency groupIdweblogic/groupId artifactIdwlsybase/artifactId version1.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/wlsybase.jar/systemPath /dependency dependency groupIdweblogic/groupId artifactIdjms510/artifactId version8.1.4.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/jms510.jar/systemPath /dependency dependency groupIdjavax.net.ssl/groupId artifactIdjsse/artifactId version1.4.2/version scopesystem/scope systemPath${java1_4.home}/jre/lib/jsse.jar/systemPath /dependency Properties are defined in profile in settings.xml and the profile activated. The project builds when we run it through command line or eclipse without enabling dependency management of M2 plugin. Any help on this would be greatly appreceated. Regards Maruf - 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: m2eclipse plugin does not resolve properties from settings.xml
Jeff Jensen wrote: And you are using the dev version of m2eclipse? If not, you should - it's more stable than the official release. Please elaborate on this. Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: m2eclipse plugin does not resolve properties from settings.xml
Thanks for your quick reply on this. I am using latest from http://m2eclipse.sonatype.org/update-dev/site. I use maven external. as C:\apache-maven-2.1.0 and defined both global and user setiings as C:\apache-maven-2.1.0/conf/settings.xml Eclipse version: Version: 3.4.2 Build id: M20090211-1700 Eclipse runs in jdk 1.5 Project build jdk 1.4 I did run mvn install on command line as well as from eclips emaven run. Here is what I did: Checke dout project from CVS run mvn install run mvn eclipse:eclipse Enabled M2 plugin dependency management and got the error I specicied below. I remember getting this working for other projects in my previous company. Do you think eclipse version does matter? Thanks, Maruf -Original Message- From: Jeff Jensen [mailto:jeffjen...@upstairstechnology.com] Sent: Monday, January 11, 2010 3:02 PM To: 'Maven Users List' Subject: RE: m2eclipse plugin does not resolve properties from settings.xml Any help on this would be greatly appreceated. Something to try - have you done a mvn install from the CLI for it (you mention the build works, but not which goal, so thought I would mention it)? A few times I've had unexplainable build problems when first setting up a new Eclipse workspace with an existing product. After a mvn install, things are magically better. And you are using the dev version of m2eclipse? If not, you should - it's more stable than the official release. -Original Message- From: Maruf Aytekin [mailto:aayte...@gmail.com] Sent: Monday, January 11, 2010 5:59 AM To: users@maven.apache.org Subject: m2eclipse plugin does not resolve properties from settings.xml Hi there, We are using m2eclipse plugin for our maven2 project in eclipse. It seems it cannot resolve properties from settings file. When we enabled Dependency Management for M2 plugin it gives errors for the main pom.xml that cannot resolve systempath for the dependencies in system scope. Here is the errors Eclipse produces when enabled dependency management of M2 plugin: - Project build error: For dependency weblogic:weblogic:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/weblogic.jar - Project build error: For dependency weblogic:webservices:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/webservices.jar - Project build error: For dependency weblogic:jms510:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/jms510.jar - Project build error: For dependency weblogic:wlsybase:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/wlsybase.jar - Project build error: For dependency javax.net.ssl:jsse:jar: system-scoped dependency must specify an absolute systemPath but is ${java1_4.home}/jre/lib/jsse.jar The dependencies defined in the main pom.xml as follows: dependency groupIdweblogic/groupId artifactIdweblogic/artifactId version8.1.4.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/weblogic.jar/systemPath /dependency dependency groupIdweblogic/groupId artifactIdwebservices/artifactId version1.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/webservices.jar/systemPath /dependency dependency groupIdweblogic/groupId artifactIdwlsybase/artifactId version1.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/wlsybase.jar/systemPath /dependency dependency groupIdweblogic/groupId artifactIdjms510/artifactId version8.1.4.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/jms510.jar/systemPath /dependency dependency groupIdjavax.net.ssl/groupId artifactIdjsse/artifactId version1.4.2/version scopesystem/scope systemPath${java1_4.home}/jre/lib/jsse.jar/systemPath /dependency Properties are defined in profile in settings.xml and the profile activated. The project builds when we run it through command line or eclipse without enabling dependency management of M2 plugin. Any help on this would be greatly appreceated. Regards Maruf - 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
How to customize the project info reports-project-info-reports:project-team
Hi All, I am generating the site through site goal.The project-team list page contains some info which is not suitable for all type of project.Examle- The Team A successful project requires many people to play many roles. Some members write code or documentation, while others are valuable as testers, submitting patches and suggestions. The team is comprised of Members and Contributors. Members have direct access to the source of a project and actively evolve the code-base. Contributors improve the project through submission of patches and suggestions to the Members. The number of Contributors to the project is unbounded. Get involved today. All contributions to the project are greatly appreciated. Above is required for a opensource project.I want only the table.How can i remove this part? Thanks, Debasis -- View this message in context: http://old.nabble.com/How-to-customize-the-project-info-reports-project-info-reports%3Aproject-team-tp27110499p27110499.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: Resource filtering difficulties.
Your solution actually gave me a NullPointerException (in plexus-filtering), because ${*} is replaced by the value of property * in the pom. So you have to use delimiter$${*}/delimiter (It took me a while to figure out that the ${ } is escaped by doubling the dollar sign :-)) Here's the jira issue I filed for improving the docs: http://jira.codehaus.org/browse/MRESOURCES-115 Regards, Karel On Mon, Jan 11, 2010 at 9:08 AM, Karel Vervaeke ka...@outerthought.org wrote: Thanks! On Sat, Jan 9, 2010 at 5:36 PM, Olivier Lamy ol...@apache.org wrote: Hi, You can try with configuring the resources mojo as this : useDefaultDelimitersfalse/useDefaultDelimiters delimiters delimiter${*}/delimiter /delimiters The @ won't be use as delimiter. -- Olivier 2010/1/8 Karel Vervaeke ka...@outerthought.org: I'm having difficulties with resource filtering In my pom I have: resource targetPathsome path/targetPath filteringtrue/filtering directory${basedir}/src/main/xpatch/directory includesinclude*/include/includes /resource plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId configuration escapeString\/escapeString /configuration /plugin in src/main/xpatch I have: ?xml version=1.0? patches xmlns:map=http://apache.org/cocoon/sitemap/1.0; patch xpath=/runtime/containers remove=artifa...@id='competent']/ patch xpath=/runtime/containers remove=artifa...@id='doctasks']/ patch xpath=/runtime/containers insert-after=artifa...@id='workflow'] artifact id=doctasks groupId=daisy artifactId=daisy-doctaskrunner-server-impl version=${myversion}/ artifact id=doctasks groupId=daisy artifactId=daisy-doctaskrunner-server-impl version=${myversion} / artifact id=workflow groupId=daisy artifactId=daisy-workflow-server-impl version=${myversion}/ /patch /patches In the output, ${myversion} is not replaced. I have determined that the problem is caused by the fact that the @ is also a I have also tried escaping the @ using the escape string defined in the pom, but then the output looks like this:: patch xpath=/runtime/containers remove=artifa...@id='competent']/ patch xpath=/runtime/containers remove=artifac...@id='doctasks']/ patch xpath=/runtime/containers insert-after=artifac...@id='workflow'] ... (The first \@ is escaped, but for the others nothing happens. IIUC this has to do with the fact that the escape string is used to escape pairs of at signs, but that seems like a strange way to handle things). I found some more info here: http://maven.apache.org/shared/maven-filtering/, but nothing that helped In the end I ended up defining a property at=@ and using ${at} in my resource, which works but isn't very nice. Does anyone have ideas about this? Regards, Karel0 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier - 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
maven install goal on remote server
Hi, I'm trying to configure the hudson ci server to retrieve a maven project from the SCM and then build/test/install it on an integration server. is it possible to tell maven that for a certain goal (e.g install remote) so that the hudson will install it on a remote server? (i can then run the 'post build task' plugin and run a shell script to activate certain tests...). right now i use 'copy-dependencies' and 'copy-resources' for installing a project on the local machine (see POM below) is there a way to it remotly? thanks! ?xml version=1.0 encoding=utf-8? 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 groupIdcom.company.url.unknowns/groupId artifactIdIncreasePriority/artifactId packagingjar/packaging version0.0.2/version nameIncreasePriority/name parent groupIdcom.company.maven.pom/groupId artifactIdWebSecParent/artifactId version0.0.2/version /parent build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId executions execution idcopy-dependencies/id phasepackage/phase goals goalcopy-dependencies/goal /goals configuration outputDirectory/usr/lib/ctch/java//outputDirectory overWriteReleasestrue/overWriteReleases overWriteSnapshotstrue/overWriteSnapshots overWriteIfNewertrue/overWriteIfNewer /configuration /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId executions execution idcopy-conf/id phaseinstall/phase goals goalcopy-resources/goal /goals configuration outputDirectory/etc/ct-urlf-increase-priority//outputDirectory resources resource directorysrc/main/resources/directory filteringtrue/filtering includes include**/*.properties/include /includes /resource /resources /configuration /execution execution idcopy-cron/id phaseinstall/phase goals goalcopy-resources/goal /goals configuration outputDirectory/etc/cron.d//outputDirectory resources resource directorysrc/main/resources/directory filteringtrue/filtering includes include**/*.cron/include /includes /resource /resources /configuration /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration outputDirectory/usr/local/ct-urlf-increase-priority/outputDirectory archive manifest mainClasscom.company.url.unknowns.IncreasePriority/mainClass addClasspathtrue/addClasspath classpathPrefix/usr/lib/ctch/java//classpathPrefix /manifest /archive /configuration /plugin /plugins /build dependencies dependency groupIdjavax.mail/groupId artifactIdmail/artifactId version1.4.1/version /dependency dependency groupIdcom.company.sql/groupId artifactIdDbUtil/artifactId version0.0.4/version /dependency /dependencies /project -- Eyal Edri
Re: How to customize the project info reports-project-info-reports:project-team
On Mon, 2010-01-11 at 05:35 -0800, DebasisM wrote: Hi All, I am generating the site through site goal.The project-team list page contains some info which is not suitable for all type of project.Examle- The Team A successful project requires many people to play many roles. Some members write code or documentation, while others are valuable as testers, submitting patches and suggestions. The team is comprised of Members and Contributors. Members have direct access to the source of a project and actively evolve the code-base. Contributors improve the project through submission of patches and suggestions to the Members. The number of Contributors to the project is unbounded. Get involved today. All contributions to the project are greatly appreciated. Above is required for a opensource project.I want only the table.How can i remove this part? Thanks, Debasis I seem to remember adding a patch for this a while back - http://jira.codehaus.org/browse/MPIR-35 The text you mention is contained in a properties file. I added a mojo param to allow you to specify a custom file location. Adam -- Adam Leggett Chief Architect Mike CI - Hosted Continuous Integration http://mikeci.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
out of memory error while generating the sites
Hi All, when through my eclipse i am generating the sites it is going well.But through hudson i am encountering with the following error.I am executing site-deploy goal [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Java heap space [INFO] [INFO] Trace java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOfRange(Unknown Source) at java.lang.String.init(Unknown Source) at java.io.DataInputStream.readUTF(Unknown Source) at java.io.DataInputStream.readUTF(Unknown Source) at org.apache.bcel.classfile.ConstantUtf8.init(ConstantUtf8.java:54) at org.apache.bcel.classfile.Constant.readConstant(Constant.java:144) at org.apache.bcel.classfile.ConstantPool.init(ConstantPool.java:67) at org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:222) at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:136) at org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:92) at org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:286) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1389) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:533) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:274) at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79) at org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:239) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:93) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.maven.agent.ComponentInterceptor.invoke(ComponentInterceptor.java:47) at hudson.maven.agent.PluginManagerInterceptor$3.invoke(PluginManagerInterceptor.java:228) at $Proxy4.generate(Unknown Source) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) [INFO] [INFO] Total time: 37 seconds [INFO] Finished at: Mon Jan 11 20:53:08 IST 2010 [INFO] Final Memory: 27M/63M [INFO] channel stopped Finished: FAILURE Thanks, Debasis -- View this message in context: http://old.nabble.com/out-of-memory-error-while-generating-the-sites-tp27112298p27112298.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 shade plugin: behavior change from 1.2.2 to 1.3?
I am gently abusing the maven-shade-plugin for some code generation behavior. When I upgraded from version 1.2.2 to version 1.3 something broke. In our project, we (unfortunately IMHO) rely a lot on code generation. But we also allow our customers to write their own hand-crafted overrides of code. We build the generated code in one maven project, and the hand crafted code in another. At the end of this mess, our desire was to have a single jar whose base layer consists of all the generated code, which would then be seletively overlaid by the hand crafted code. This would, in other words, replace any generated classes with handcrafted classes where such handcrafted classes exist. So suppose we generate com/foo/ABase.java, and com/foo/A.java, an empty class that inherits from ABase.java. We create a generated.jar for that containing com.foo.ABase and com.foo.A. This way if the customer doesn't do anything, our system still knows about A, even though A is just empty and is effectively entirely defined by the contents of its superclass. Then in our handcrafted project, suppose that a customer has created simply com/foo/A.java. We originally had this set up so that the maven-shade-plugin got involved and effectively merged the two jars: after building the handcrafted project, which by default produces a jar with one class in it, namely com.foo.A, maven shade steps in and produces a shaded jar whose contents include the generated com.foo.ABase and the handcrafted com.foo.A. This all worked fine in version 1.2.2. The maven shade plugin outputs a warning that says effectively, Um, hey, you're going to stomp all over an existing A class with this new A class you just compiled, I hope that's OK. In version 1.3, no such warning is output, and in fact the overlaying/overwriting does not occur. I did not read anything one way or the other in the maven-shade-plugin documentation which led me to believe that any aspect of this behavior was defined. Can someone tell me what the intended behavior is in the case where you wish to shade a class with the same name? In 1.3 this does not appear to work at all. Thanks as always for your time and for an excellent build system. Best, Laird
maven-ear-plugin: MEAR-85 patch
Hi, I'm looking for possibility to commit the patch which solves MEAR-85 [1] issue in EAR plugin. I have pretty huge project driven by Maven and having workarounds there seem to be painful. I don't also want to have my own patched version of maven-ear-plugin. I had provided the patch which solves the issue [2], is there something I can do to make it appear in SNAPSHOT faster? Of course, if the patch is correct. Thanks, Aleksey. [1] http://jira.codehaus.org/browse/MEAR-85 [2] http://jira.codehaus.org/browse/MEAR-85?focusedCommentId=205548page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_205548 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven: Groupings surfire tests results in one directory ? -DreportsDirectory= ignored ?
Hello all. I have searched the docs and web and archives but can not get a solution to work from command line. Am I missing something ? Any pointer to a potential solution ? Here is what I would like to achieve : group all tests results generated by Surfire for many Maven artefacts in one directory only, specified on the command line. I am using Maven 2.0.10 + maven-surefire-plugin 2.4.3 From the docs : Specifying on the command line -DreportsDirectory=ccc/yyy/zzz could be a solution. But it is never being taken into account. It does not work for me. This Re: setting surefire reports directory http://mail-archives.apache.org/mod_mbox/maven-users/200903.mbox/%3c49ca44c7.9020...@mgm-tp.com%3e did not help. This pom.xml attempt works, but I have no control over projects poms so it seams no to be a solution : build plugins plugin artifactIdmaven-surefire-plugin/artifactId version2.4.3/version inheritedtrue/inherited configuration reportsDirectory${basedir}/../surefire-reports/reportsDirectory ... /configuration /plugin /plugins /build Regards and thanks for time and attention. G.
Re: maven-ear-plugin: MEAR-85 patch
and having workarounds there seem to be painful. I don't also want to have my own patched version of maven-ear-plugin. Why not? There is no good reason why you couldn't produce your own internally-versioned m-e-p (either a Snapshot or a real version 2.4.1ALEKSEY) assuming you have your own MRM set up (Nexus, Artifactory, etc). This is a pretty common usage pattern for Maven plugins IME, so you might as well get comfortable with it now. I had provided the patch which solves the issue [2], is there something I can do to make it appear in SNAPSHOT faster? Of course, if the patch is correct. The patch alone is not sufficient. To make it appear faster, you also need to provide tests that demonstrate the functionality works as intended etc. Finally, the ear plugin did not appear to get many votes the last time a survey was performed, so I'm unsure when that will be released next. Take a look at this thread: date: Fri, Dec 18, 2009 at 1:45 PM subject: [SURVEY] Which plugins would you like us to release? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-ear-plugin: MEAR-85 patch
Hi Wayne, On Mon, Jan 11, 2010 at 7:26 PM, Wayne Fay wayne...@gmail.com wrote: Why not? There is no good reason why you couldn't produce your own internally-versioned m-e-p This could spin off to theological discussion :) IMO, having custom-patched components is much worse than pushing the patch upstream, especially when the patch is trivial and problem manifests in large number of cases (10 votes just for that issue). Even though I could make my own patched version, it just feels right to get this in upstream. The patch alone is not sufficient. To make it appear faster, you also need to provide tests that demonstrate the functionality works as intended etc. Ok, taking off the tests, is there something else? I'd like to hear from EAR plugin committers (Stephane?) on this. Finally, the ear plugin did not appear to get many votes the last time a survey was performed, so I'm unsure when that will be released next. I would be happy with SNAPSHOT version of the plugin, not the named release. Doesn't snapshot version contain the latest code from the SVN trunk? Thanks, Aleksey. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: eroor in executin compile on hibernate project.
I am not able to find any relevent answer till now. In eclispe this project is working well without any error. So i think this is something with meven compiler. But not aware of What? will you please describe the reason for me? Eclipse has its own compiler. Maven does not -- it uses the Javac compiler included with the JDK you have installed. So there is no problem with the Maven compiler, rather it is likely you have found a problem in the Eclipse compiler, which does not complain about a bad file when it should. my package-info.java class This does not appear to be a valid Package Comment file per the Javadoc documentation, specifically the import statements are invalid. Read more online: http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#packagecomment package-info.java - Can contain a package declaration, package annotations, package comments and Javadoc tags. This file is new in JDK 5.0, and is preferred over package.html. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: out of memory error while generating the sites
when through my eclipse i am generating the sites it is going well.But through hudson i am encountering with the following error.I am executing site-deploy goal [INFO] Trace java.lang.OutOfMemoryError: Java heap space This is a common question. http://www.lmgtfy.com/?q=maven+site+outofmemory Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: No more com.oracle.ojdbc14-10.2.0.2.0.jar ?
From my knowledge, this is not an Open Source artifact so it may not be available on central or codehaus. Where did you get it from ? Jeff MAURY On Mon, Jan 11, 2010 at 6:07 PM, HARDION Vincent vincent.hard...@synchrotron-soleil.fr wrote: Hi everybody, Since this morning, the artifact com.oracle.ojdbc14-10.2.0.2.0.jar was not found anymore!!! But the pom and the fingerprints was Can someone explain to me why ? Thank you very much and happy new year Vincent Hardion Synchrotron Soleil L'Orme des merisiers - Saint Aubin BP48 - 91192 Gif sur Yvette Tel : +33 1 69 35 93 39 -- http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.lastfm.fr/listen/user/jeffmaury/personal
Re: No more com.oracle.ojdbc14-10.2.0.2.0.jar ?
Since this morning, the artifact com.oracle.ojdbc14-10.2.0.2.0.jar was not found anymore!!! But the pom and the fingerprints was I don't believe the ojdbc jar files have ever been hosted on Central due to Oracle's licensing of those files which limits redistribution. What makes you think the jar was ever hosted there? In all likelihood, you previously using install:install-file to copy the file to your local repo and simply forgot, or someone else in your company used deploy:deploy-file to copy the file to your MRM. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: No more com.oracle.ojdbc14-10.2.0.2.0.jar ?
Wayne, have a look at http://repo2.maven.org/maven2/com/oracle/ojdbc14/10.2.0.2.0/ What The F**k are the .md5 files for the jar doing there and no .jar? -Stephen 2010/1/11 Wayne Fay wayne...@gmail.com: Since this morning, the artifact com.oracle.ojdbc14-10.2.0.2.0.jar was not found anymore!!! But the pom and the fingerprints was I don't believe the ojdbc jar files have ever been hosted on Central due to Oracle's licensing of those files which limits redistribution. What makes you think the jar was ever hosted there? In all likelihood, you previously using install:install-file to copy the file to your local repo and simply forgot, or someone else in your company used deploy:deploy-file to copy the file to your MRM. Wayne - 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: eroor in executin compile on hibernate project.
Hi; The project i have got is legacy project and all hibernate queries are defined like that only(in package-info.java). So; I am not sure whether it is standard or i need to tweak something with compiler. Is there any option exists so i can do a compiling. :) Regards, Vijay Shanker Dubey On Mon, Jan 11, 2010 at 10:08 PM, Wayne Fay wayne...@gmail.com wrote: I am not able to find any relevent answer till now. In eclispe this project is working well without any error. So i think this is something with meven compiler. But not aware of What? will you please describe the reason for me? Eclipse has its own compiler. Maven does not -- it uses the Javac compiler included with the JDK you have installed. So there is no problem with the Maven compiler, rather it is likely you have found a problem in the Eclipse compiler, which does not complain about a bad file when it should. my package-info.java class This does not appear to be a valid Package Comment file per the Javadoc documentation, specifically the import statements are invalid. Read more online: http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#packagecomment package-info.java - Can contain a package declaration, package annotations, package comments and Javadoc tags. This file is new in JDK 5.0, and is preferred over package.html. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: No more com.oracle.ojdbc14-10.2.0.2.0.jar ?
What The F**k are the .md5 files for the jar doing there and no .jar? Yea, I noticed that too, and definitely find it odd. Perhaps someone pushed the files there accidentally at some point? We probably need Carlos or another repo maintainer to make a comment. It is possible the Jar was there (perhaps briefly) at some point and was subsequently deleted due to licensing etc upon notification by Oracle? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: eroor in executin compile on hibernate project.
The project i have got is legacy project and all hibernate queries are defined like that only(in package-info.java). So; I am not sure whether it is standard or i need to tweak something with compiler. This is a question for the Hibernate list. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: eroor in executin compile on hibernate project.
You can fix your package-info.java. I'd start by adding a package declaration (which you appear to be missing) and using fully-qualified class names for the annotations. Alternatively, you can use the Eclipse compiler instead of javac: http://maven.apache.org/plugins/maven-compiler-plugin/non-javac-compilers.html There are differences between the Eclipse compiler and javac. They're not common, but they do exist. Justin On Mon, Jan 11, 2010 at 12:46 PM, vijay shanker vijay.s...@gmail.comwrote: Hi; The project i have got is legacy project and all hibernate queries are defined like that only(in package-info.java). So; I am not sure whether it is standard or i need to tweak something with compiler. Is there any option exists so i can do a compiling. :) Regards, Vijay Shanker Dubey On Mon, Jan 11, 2010 at 10:08 PM, Wayne Fay wayne...@gmail.com wrote: I am not able to find any relevent answer till now. In eclispe this project is working well without any error. So i think this is something with meven compiler. But not aware of What? will you please describe the reason for me? Eclipse has its own compiler. Maven does not -- it uses the Javac compiler included with the JDK you have installed. So there is no problem with the Maven compiler, rather it is likely you have found a problem in the Eclipse compiler, which does not complain about a bad file when it should. my package-info.java class This does not appear to be a valid Package Comment file per the Javadoc documentation, specifically the import statements are invalid. Read more online: http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#packagecomment package-info.java - Can contain a package declaration, package annotations, package comments and Javadoc tags. This file is new in JDK 5.0, and is preferred over package.html. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: eroor in executin compile on hibernate project.
Thanks guys; I am digging in to the matter. Regards, Vijay Shanker Dubey On Mon, Jan 11, 2010 at 11:29 PM, Justin Edelson justinedel...@gmail.comwrote: You can fix your package-info.java. I'd start by adding a package declaration (which you appear to be missing) and using fully-qualified class names for the annotations. Alternatively, you can use the Eclipse compiler instead of javac: http://maven.apache.org/plugins/maven-compiler-plugin/non-javac-compilers.html There are differences between the Eclipse compiler and javac. They're not common, but they do exist. Justin On Mon, Jan 11, 2010 at 12:46 PM, vijay shanker vijay.s...@gmail.com wrote: Hi; The project i have got is legacy project and all hibernate queries are defined like that only(in package-info.java). So; I am not sure whether it is standard or i need to tweak something with compiler. Is there any option exists so i can do a compiling. :) Regards, Vijay Shanker Dubey On Mon, Jan 11, 2010 at 10:08 PM, Wayne Fay wayne...@gmail.com wrote: I am not able to find any relevent answer till now. In eclispe this project is working well without any error. So i think this is something with meven compiler. But not aware of What? will you please describe the reason for me? Eclipse has its own compiler. Maven does not -- it uses the Javac compiler included with the JDK you have installed. So there is no problem with the Maven compiler, rather it is likely you have found a problem in the Eclipse compiler, which does not complain about a bad file when it should. my package-info.java class This does not appear to be a valid Package Comment file per the Javadoc documentation, specifically the import statements are invalid. Read more online: http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#packagecomment package-info.java - Can contain a package declaration, package annotations, package comments and Javadoc tags. This file is new in JDK 5.0, and is preferred over package.html. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: No more com.oracle.ojdbc14-10.2.0.2.0.jar ?
I did it some time ago as this was condidered a good practice : define a common POM and checksums for artifacts that are not freely redistribuable, but that user may include in a custom repo. There is some other entries en central like this one (metadatas without jar) 2010/1/11 Wayne Fay wayne...@gmail.com What The F**k are the .md5 files for the jar doing there and no .jar? Yea, I noticed that too, and definitely find it odd. Perhaps someone pushed the files there accidentally at some point? We probably need Carlos or another repo maintainer to make a comment. It is possible the Jar was there (perhaps briefly) at some point and was subsequently deleted due to licensing etc upon notification by Oracle? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: No more com.oracle.ojdbc14-10.2.0.2.0.jar ?
i may have added the checksums. It allows to check that the jar matches what was supposed to be in the repo but can't be for legal reasons. On Mon, Jan 11, 2010 at 1:09 PM, nicolas de loof nicolas.del...@gmail.com wrote: I did it some time ago as this was condidered a good practice : define a common POM and checksums for artifacts that are not freely redistribuable, but that user may include in a custom repo. There is some other entries en central like this one (metadatas without jar) 2010/1/11 Wayne Fay wayne...@gmail.com What The F**k are the .md5 files for the jar doing there and no .jar? Yea, I noticed that too, and definitely find it odd. Perhaps someone pushed the files there accidentally at some point? We probably need Carlos or another repo maintainer to make a comment. It is possible the Jar was there (perhaps briefly) at some point and was subsequently deleted due to licensing etc upon notification by Oracle? Wayne - 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: No more com.oracle.ojdbc14-10.2.0.2.0.jar ?
I agree with pushing poms. I'm less inclined to agree with the checksums... but that's OK, I don't really care either way. Now back to Vincent... what makes you think this jar file EVER existed in Central?? Wayne On Mon, Jan 11, 2010 at 3:09 PM, nicolas de loof nicolas.del...@gmail.com wrote: I did it some time ago as this was condidered a good practice : define a common POM and checksums for artifacts that are not freely redistribuable, but that user may include in a custom repo. There is some other entries en central like this one (metadatas without jar) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven shade plugin: behavior change from 1.2.2 to 1.3?
I believe you are correct. Thanks for the bug reference. I'm pinning to 1.2.2 as well. Best, Laird On Mon, Jan 11, 2010 at 2:19 PM, Mat Johns m...@cyberfish.org wrote: I think you maybe having the same problem as me. It looks like when specifying a particular set of artifacts to include in the shaded jar ... artifactSet includes includegroupId:artifactId/include /includes /artifactSet ... it excludes the current package from the final shaded jar (which I think is a bug, as its not shading it; rather than shading into it); and as such have filed a bug on their jira. http://jira.codehaus.org/browse/MSHADE-72 For the moment I have update my builds to pin to the 1.2.2 version ... build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-shade-plugin/artifactId version1.2.2/version ... /plugin /plugins /build ... this at least works around the issue for now. Regard ~Mat Laird Nelson wrote: I am gently abusing the maven-shade-plugin for some code generation behavior. When I upgraded from version 1.2.2 to version 1.3 something broke. In our project, we (unfortunately IMHO) rely a lot on code generation. But we also allow our customers to write their own hand-crafted overrides of code. We build the generated code in one maven project, and the hand crafted code in another. At the end of this mess, our desire was to have a single jar whose base layer consists of all the generated code, which would then be seletively overlaid by the hand crafted code. This would, in other words, replace any generated classes with handcrafted classes where such handcrafted classes exist. So suppose we generate com/foo/ABase.java, and com/foo/A.java, an empty class that inherits from ABase.java. We create a generated.jar for that containing com.foo.ABase and com.foo.A. This way if the customer doesn't do anything, our system still knows about A, even though A is just empty and is effectively entirely defined by the contents of its superclass. Then in our handcrafted project, suppose that a customer has created simply com/foo/A.java. We originally had this set up so that the maven-shade-plugin got involved and effectively merged the two jars: after building the handcrafted project, which by default produces a jar with one class in it, namely com.foo.A, maven shade steps in and produces a shaded jar whose contents include the generated com.foo.ABase and the handcrafted com.foo.A. This all worked fine in version 1.2.2. The maven shade plugin outputs a warning that says effectively, Um, hey, you're going to stomp all over an existing A class with this new A class you just compiled, I hope that's OK. In version 1.3, no such warning is output, and in fact the overlaying/overwriting does not occur. I did not read anything one way or the other in the maven-shade-plugin documentation which led me to believe that any aspect of this behavior was defined. Can someone tell me what the intended behavior is in the case where you wish to shade a class with the same name? In 1.3 this does not appear to work at all. Thanks as always for your time and for an excellent build system. Best, Laird
RE: m2eclipse plugin does not resolve properties from settings.xml
If using m2eclipse, forget about eclipse:eclipse. To setup a new Eclipse workspace (with no Eclipse config files existing, i.e. .classpath, .project; delete them to start fresh), start Eclipse to an empty workspace, have m2eclipse and other plugins installed, then choose File - Import - Maven - Existing Maven Projects and follow the wizard. This option nicely realizes the projects, creates the Eclipse config files, and manages the workspace (including resolving deps). To continue from where you are, possibly Maven - Update Project Configuration on the project context menu may clear things up (do for each Eclipse project). Rarely/occasionally manually invoking that is needed (not sure why, but things get a little out of sync and that fixes it for me). I used Eclipse 3.4 successfully with m2eclipse. For the past 2 months, have successfully been using 3.5 (Galileo) though. The dev version of m2eclipse uses Maven 3. If the above doesn't fix, try _not_ using the external - use the embedded version and see if the problem goes away. -Original Message- From: Maruf Aytekin [mailto:aayte...@gmail.com] Sent: Monday, January 11, 2010 7:34 AM To: users@maven.apache.org Subject: RE: m2eclipse plugin does not resolve properties from settings.xml Thanks for your quick reply on this. I am using latest from http://m2eclipse.sonatype.org/update-dev/site. I use maven external. as C:\apache-maven-2.1.0 and defined both global and user setiings as C:\apache-maven-2.1.0/conf/settings.xml Eclipse version: Version: 3.4.2 Build id: M20090211-1700 Eclipse runs in jdk 1.5 Project build jdk 1.4 I did run mvn install on command line as well as from eclips emaven run. Here is what I did: Checke dout project from CVS run mvn install run mvn eclipse:eclipse Enabled M2 plugin dependency management and got the error I specicied below. I remember getting this working for other projects in my previous company. Do you think eclipse version does matter? Thanks, Maruf -Original Message- From: Jeff Jensen [mailto:jeffjen...@upstairstechnology.com] Sent: Monday, January 11, 2010 3:02 PM To: 'Maven Users List' Subject: RE: m2eclipse plugin does not resolve properties from settings.xml Any help on this would be greatly appreceated. Something to try - have you done a mvn install from the CLI for it (you mention the build works, but not which goal, so thought I would mention it)? A few times I've had unexplainable build problems when first setting up a new Eclipse workspace with an existing product. After a mvn install, things are magically better. And you are using the dev version of m2eclipse? If not, you should - it's more stable than the official release. -Original Message- From: Maruf Aytekin [mailto:aayte...@gmail.com] Sent: Monday, January 11, 2010 5:59 AM To: users@maven.apache.org Subject: m2eclipse plugin does not resolve properties from settings.xml Hi there, We are using m2eclipse plugin for our maven2 project in eclipse. It seems it cannot resolve properties from settings file. When we enabled Dependency Management for M2 plugin it gives errors for the main pom.xml that cannot resolve systempath for the dependencies in system scope. Here is the errors Eclipse produces when enabled dependency management of M2 plugin: - Project build error: For dependency weblogic:weblogic:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/weblogic.jar - Project build error: For dependency weblogic:webservices:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/webservices.jar - Project build error: For dependency weblogic:jms510:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/jms510.jar - Project build error: For dependency weblogic:wlsybase:jar: system-scoped dependency must specify an absolute systemPath but is ${local_bea_home}/server/lib/wlsybase.jar - Project build error: For dependency javax.net.ssl:jsse:jar: system-scoped dependency must specify an absolute systemPath but is ${java1_4.home}/jre/lib/jsse.jar The dependencies defined in the main pom.xml as follows: dependency groupIdweblogic/groupId artifactIdweblogic/artifactId version8.1.4.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/weblogic.jar/systemPath /dependency dependency groupIdweblogic/groupId artifactIdwebservices/artifactId version1.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/webservices.jar/systemPath /dependency dependency groupIdweblogic/groupId artifactIdwlsybase/artifactId version1.0/version scopesystem/scope systemPath${local_bea_home}/server/lib/wlsybase.jar/systemPath /dependency dependency groupIdweblogic/groupId artifactIdjms510/artifactId
RE: m2eclipse plugin does not resolve properties from settings.xml
It's been months since I switched, so don't remember details. What I do recall is having less something's messed up and I don't know what it is problems with the dev version. The dev version uses Maven 3 embedder, and, per the dev list, Maven 3 alphas are proving to be more robust than Maven 2. So couple the Maven 3 quality with the efforts a few of the devs have put into m2eclipse, your experience should be (TM) better with the dev version too. However, if you are not having troubles with the latest release version, then stay with it... if it ain't broke -Original Message- From: Steve Cohen [mailto:sco...@javactivity.org] Sent: Monday, January 11, 2010 7:19 AM To: Maven Users List Subject: Re: m2eclipse plugin does not resolve properties from settings.xml Jeff Jensen wrote: And you are using the dev version of m2eclipse? If not, you should - it's more stable than the official release. Please elaborate on this. Thanks. - 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
mAVEN BUILD ERROR
MVEN IS GIVING THE FOLLOWING ERROR ON COMMAND PROMPT [INFO] Compilation failure Failure executing javac, but could not parse the error: Fatal Error: Unable to find package java.lang in classpath or bootclasspath Failure executing javac, but could not parse the error: Fatal Error: Unable to find package java.lang in classpath or bootclasspath My windows version is win xp service pack 2 maven ver - 2.0.9-maestro-1.7.6 JAVA_HOME = JDK1.6.0_16 JRE_HOME IS SET M2_POST IS SET RAD 7.* IS CONFIGURED PLESSE HELP -- View this message in context: http://old.nabble.com/mAVEN-BUILD-ERROR-tp27123082p27123082.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