Archiva crashes after a couple of days
I am running the standalone archiva and I have about 4 managed repositories (including a proxy repo), and about 6 or 7 remote repositories. I create a single proxy connector to all of the remote repositories and changed my settings.xml to be a mirrorOf *. Currently, I only have my Continuous Integration box configured to use Archiva as a proxy and I am finding that it crashes every couple of days. Also, I am running all of default consumers and I do see the bug about invalid path for some artifacts (Bret Porter closed the bug yesterday and the fix will be in 1.0.2). Has anyone else seen this? Any ideas?
RE: Archiva crashes after a couple of days
I am running on RedHat Enterprise 4 update 4. It has crashed on m2 at least 6 times in the last two weeks and I am not doing anything special with it. Also, I have noticed that it is creating almost 5 Gigs in logs files a day. I wonder if this has anything to do with it. -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 12:45 PM To: archiva-users@maven.apache.org Subject: Re: Archiva crashes after a couple of days Jason, I can tell you that we've had our Archiva instance up and running for at least 3+ weeks without having to restart. We have 5 repositories and about 6 remote repositories and we too are using the standalone product and nearly all consumers. What platform are you running on? Eric On Fri, 2008-02-22 at 12:40 -0800, Jason Chaffee wrote: I am running the standalone archiva and I have about 4 managed repositories (including a proxy repo), and about 6 or 7 remote repositories. I create a single proxy connector to all of the remote repositories and changed my settings.xml to be a mirrorOf *. Currently, I only have my Continuous Integration box configured to use Archiva as a proxy and I am finding that it crashes every couple of days. Also, I am running all of default consumers and I do see the bug about invalid path for some artifacts (Bret Porter closed the bug yesterday and the fix will be in 1.0.2). Has anyone else seen this? Any ideas?
RE: Archiva crashes after a couple of days
I too had this same issue. Make sure your cron syntax is correct as it is not standard unix cron syntax. The first entry is a second number, not minutes. I initially (and accidentally) setup our cron jobs to run at a crazy pace, I think every second. I asked the mailing list if there was a way to clear these queue of events so I could let the app run its course, but received no answers. i eventually had to reinstall fresh to get around it but all works great now. FYI, we're on RHEL 4 update 4 as well. Eric On Fri, 2008-02-22 at 13:01 -0800, Jason Chaffee wrote: I am running on RedHat Enterprise 4 update 4. It has crashed on m2 at least 6 times in the last two weeks and I am not doing anything special with it. Also, I have noticed that it is creating almost 5 Gigs in logs files a day. I wonder if this has anything to do with it. -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 12:45 PM To: archiva-users@maven.apache.org Subject: Re: Archiva crashes after a couple of days Jason, I can tell you that we've had our Archiva instance up and running for at least 3+ weeks without having to restart. We have 5 repositories and about 6 remote repositories and we too are using the standalone product and nearly all consumers. What platform are you running on? Eric On Fri, 2008-02-22 at 12:40 -0800, Jason Chaffee wrote: I am running the standalone archiva and I have about 4 managed repositories (including a proxy repo), and about 6 or 7 remote repositories. I create a single proxy connector to all of the remote repositories and changed my settings.xml to be a mirrorOf *. Currently, I only have my Continuous Integration box configured to use Archiva as a proxy and I am finding that it crashes every couple of days. Also, I am running all of default consumers and I do see the bug about invalid path for some artifacts (Bret Porter closed the bug yesterday and the fix will be in 1.0.2). Has anyone else seen this? Any ideas?
RE: Archiva crashes after a couple of days
-Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 4:07 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days I too had this same issue. Make sure your cron syntax is correct as it is not standard unix cron syntax. The first entry is a second number, not minutes. I initially (and accidentally) setup our cron jobs to run at a crazy pace, I think every second. Me three. I didn't see any reason not to scan every minute, but in fact it was every second. Result - massive log files, Archiva hung. Did not have to reinstall it, though. The cron setup would be a good candidate for improved input forms and/or validation. - This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you.
RE: Archiva crashes after a couple of days
It sounds like the default cron expressions are the culprit then. I imagine it was tested on the amount of repos and with the amount of artifacts that a big company might have and thus it causes problems. Could you give me the cron expression that you are using for repo scans and database updates? Thanks. -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 1:07 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days I too had this same issue. Make sure your cron syntax is correct as it is not standard unix cron syntax. The first entry is a second number, not minutes. I initially (and accidentally) setup our cron jobs to run at a crazy pace, I think every second. I asked the mailing list if there was a way to clear these queue of events so I could let the app run its course, but received no answers. i eventually had to reinstall fresh to get around it but all works great now. FYI, we're on RHEL 4 update 4 as well. Eric On Fri, 2008-02-22 at 13:01 -0800, Jason Chaffee wrote: I am running on RedHat Enterprise 4 update 4. It has crashed on m2 at least 6 times in the last two weeks and I am not doing anything special with it. Also, I have noticed that it is creating almost 5 Gigs in logs files a day. I wonder if this has anything to do with it. -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 12:45 PM To: archiva-users@maven.apache.org Subject: Re: Archiva crashes after a couple of days Jason, I can tell you that we've had our Archiva instance up and running for at least 3+ weeks without having to restart. We have 5 repositories and about 6 remote repositories and we too are using the standalone product and nearly all consumers. What platform are you running on? Eric On Fri, 2008-02-22 at 12:40 -0800, Jason Chaffee wrote: I am running the standalone archiva and I have about 4 managed repositories (including a proxy repo), and about 6 or 7 remote repositories. I create a single proxy connector to all of the remote repositories and changed my settings.xml to be a mirrorOf *. Currently, I only have my Continuous Integration box configured to use Archiva as a proxy and I am finding that it crashes every couple of days. Also, I am running all of default consumers and I do see the bug about invalid path for some artifacts (Bret Porter closed the bug yesterday and the fix will be in 1.0.2). Has anyone else seen this? Any ideas?
RE: Archiva crashes after a couple of days
We use: 0 30 2 * * ? - daily at 2:30 am 0 30 * * * ? - every 30 mins The default out of the box shouldn't be an issue I wouldn't think. How large are your repos? Ours: 344Mjasper 332Kplugins 203Mproxied 107Mreleases 239Msnapshots On Fri, 2008-02-22 at 13:28 -0800, Jason Chaffee wrote: I am using the defaults, out of box expressions. So, it seems those too could be fine tuned. -Original Message- From: Brown, Carlton [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 1:14 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 4:07 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days I too had this same issue. Make sure your cron syntax is correct as it is not standard unix cron syntax. The first entry is a second number, not minutes. I initially (and accidentally) setup our cron jobs to run at a crazy pace, I think every second. Me three. I didn't see any reason not to scan every minute, but in fact it was every second. Result - massive log files, Archiva hung. Did not have to reinstall it, though. The cron setup would be a good candidate for improved input forms and/or validation. - This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you.
RE: Archiva crashes after a couple of days
My schedules were definitely wrong and causing scanning often. I think this is why it was crashing. -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 1:38 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days We use: 0 30 2 * * ? - daily at 2:30 am 0 30 * * * ? - every 30 mins The default out of the box shouldn't be an issue I wouldn't think. How large are your repos? Ours: 344Mjasper 332Kplugins 203Mproxied 107Mreleases 239Msnapshots On Fri, 2008-02-22 at 13:28 -0800, Jason Chaffee wrote: I am using the defaults, out of box expressions. So, it seems those too could be fine tuned. -Original Message- From: Brown, Carlton [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 1:14 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 4:07 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days I too had this same issue. Make sure your cron syntax is correct as it is not standard unix cron syntax. The first entry is a second number, not minutes. I initially (and accidentally) setup our cron jobs to run at a crazy pace, I think every second. Me three. I didn't see any reason not to scan every minute, but in fact it was every second. Result - massive log files, Archiva hung. Did not have to reinstall it, though. The cron setup would be a good candidate for improved input forms and/or validation. - This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you.
RE: Archiva crashes after a couple of days
Wow, you got us beat. Those are pretty large repos. Maybe the Archiva team can comment on this. I'm interested to hear what they say. Eric On Fri, 2008-02-22 at 16:39 -0800, Jason Chaffee wrote: They are pretty big, both in number of artifacts and in size. Our largest repo has around 75,000 artifacts in right now and the size is over 200 GB. This is a snapshot repo and we have many teams that are creating large installer artifacts that are basically uber artifacts, thus the size of these artifacts can be quite large. -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 1:38 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days We use: 0 30 2 * * ? - daily at 2:30 am 0 30 * * * ? - every 30 mins The default out of the box shouldn't be an issue I wouldn't think. How large are your repos? Ours: 344Mjasper 332Kplugins 203Mproxied 107Mreleases 239Msnapshots On Fri, 2008-02-22 at 13:28 -0800, Jason Chaffee wrote: I am using the defaults, out of box expressions. So, it seems those too could be fine tuned. -Original Message- From: Brown, Carlton [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 1:14 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 4:07 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days I too had this same issue. Make sure your cron syntax is correct as it is not standard unix cron syntax. The first entry is a second number, not minutes. I initially (and accidentally) setup our cron jobs to run at a crazy pace, I think every second. Me three. I didn't see any reason not to scan every minute, but in fact it was every second. Result - massive log files, Archiva hung. Did not have to reinstall it, though. The cron setup would be a good candidate for improved input forms and/or validation. - This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you.
Re: maven continuum plugin
Can you open one or more issues about it. Emmanuel On Fri, Feb 22, 2008 at 9:53 AM, Benoit Decherf [EMAIL PROTECTED] wrote: Hi, I'm checking the maven continuum plugin. It will be very usefull for us. I think there are some issue in the add maven 2 goal : - The pom url : To retreive the pom, we have to point the scm.url to the exact location of the pom. That's a problem because scm.url should point to the source directory. - Why the continuum url isn't taken from ciManagement.url ? - If something doesn't work while adding the project, there is no error on the client side. The message appear only in continuum logs (maybe a probleme on the server side ?). Benoit
Re: Exploring other options outside of CruiseControl
still largely in planning phases odds are it won't take a huge effort to get things basically working but the UI elements would probably take long...they traditionally have. so...depending when one of us picks it up and runs with it, its probably a few weeks of work is all as for when it gets picked up and run with...not sure :) jesse On Fri, Feb 22, 2008 at 4:40 PM, EJ Ciramella [EMAIL PROTECTED] wrote: Hello Continuum user list! Currently, we're using CruiseControl in distributed form, but we're having issues left and right. Having our build server run in distributed from is very important. We don't like having multiple servers to visit in order to find a status and it's nice to have multiple agents (each to run their own builds). I've been over and over the continuum documentation but all I see is that distributed continuum building is a future feature. What is the status of this? -- jesse mcconnell [EMAIL PROTECTED]
RE: Exploring other options outside of CruiseControl
Is there a jira page or something where I can monitor the status? -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 5:40 PM To: continuum-users@maven.apache.org Subject: Re: Exploring other options outside of CruiseControl still largely in planning phases odds are it won't take a huge effort to get things basically working but the UI elements would probably take long...they traditionally have. so...depending when one of us picks it up and runs with it, its probably a few weeks of work is all as for when it gets picked up and run with...not sure :) jesse On Fri, Feb 22, 2008 at 4:40 PM, EJ Ciramella [EMAIL PROTECTED] wrote: Hello Continuum user list! Currently, we're using CruiseControl in distributed form, but we're having issues left and right. Having our build server run in distributed from is very important. We don't like having multiple servers to visit in order to find a status and it's nice to have multiple agents (each to run their own builds). I've been over and over the continuum documentation but all I see is that distributed continuum building is a future feature. What is the status of this? -- jesse mcconnell [EMAIL PROTECTED]
Continuum does not launch a build as scheduled?
I've two maven 2.0.8 projects that relate to the same product, one is set to retrieve and build from a branch, and the other one is set to retrieve and build from the trunk in Subversion. When I set the schedule to launch the build for each project, Continuum runs the build for the branch project, but when it attempts to launch the build as scheduled for the trunk project nothing happens, the build does not run? Instead of running the build, Continuum displays a message indicating that the project is duplicated in the reactor? But interestingly, I can force the build to run by clicking on the Build Now icon! Does anyone knows what is wrong? Here is the message that gets displayed in Apache Continuum command line screen: jvm 1| 2008-02-22 13:32:58,246 [SocketListener0-1] INFO org.apache.maven.continuum.build.settings.SchedulesActivator:default - Activating schedule MBCD 1.0 trunk Schedule jvm 1| 2008-02-22 13:32:58,261 [SocketListener0-1] INFO org.apache.maven.continuum.build.settings.SchedulesActivator:default - MBCD 1.0 trunk Schedule: next fire time -Fri Feb 22 13:34:00 PST 2008 jvm 1| There was no such logger 'com.opensymphony.xwork.Action:schedule' 040. jvm 1| 2008-02-22 13:34:00,014 [defaultScheduler_Worker-0] INFO org.apache.maven.continuum.build.settings.SchedulesActivator:default - Executing build job (MBCD 1.0 trunk Schedule)... jvm 1| 2008-02-22 13:34:00,029 [defaultScheduler_Worker-0] WARN org.apache.maven.continuum.Continuum:default - Project 'com.fairisaac.MBCD:MBCD:4.0' is duplicated in the reactor I Also, I'm using the following maven version: C:\Auto_Buildsmvn -v Maven version: 2.0.8 Java version: 1.6.0_01 OS name: windows 2003 version: 5.2 arch: x86 Family: windows Sameh This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.
Unknown error trying to build POM
Hi,
I am new to using Continuum and Maven. I've installed Continuum and am trying
add a Maven 2.0
project, but am getting an Unknown error trying to build POM. Not sure why.
Here is a skimmed down version of my pom:
project
modelVersion4.0.0/modelVersion
groupIdcom.test.tester/groupId
artifactIdacs/artifactId
packagingpom/packaging
version1.0-SNAPSHOT/version
nameacs/name
urlhttp://maven.apache.org/url
description
This is parent project. A common place to define all common
dependencies.
/description
!--
===
= BUILD SETTINGS section
===
--
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdfindbugs-maven-plugin/artifactId
version1.1.1/version
inheritedtrue/inherited
configuration
classFilesDirectory${project.build.directory}/classes/classFilesDirectory
outputDirectory${project.build.directory}/outputDirectory
xmlOutputtrue/xmlOutput
xmlOutputDirectory${project.build.directory}/xmlOutputDirectory
/configuration
/plugin
/plugins
/build
!--
===
= Dependencies section
===
--
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
dependency
groupIdcommons-httpclient/groupId
artifactIdcommons-httpclient/artifactId
version3.1/version
scopetest/scope
/dependency
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging-api/artifactId
version1.1/version
/dependency
dependency
groupIdcommons-lang/groupId
artifactIdcommons-lang/artifactId
version2.3/version
/dependency
dependency
groupIdlog4j/groupId
artifactIdlog4j/artifactId
version1.2.14/version
/dependency
dependency
groupIdmysql/groupId
artifactIdmysql-connector-java/artifactId
version5.0.4/version
/dependency
dependency
groupIdorg.springframework/groupId
artifactIdspring-mock/artifactId
version2.0.6/version
scopetest/scope
/dependency
/dependencies
modules
modulesite/module
/modules
developers
developer
nameAmish/name
/developer
/developers
/project
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
Re: Unknown error trying to build POM
On Fri, Feb 22, 2008 at 7:39 PM, Amish Shah [EMAIL PROTECTED] wrote: I am new to using Continuum and Maven. I've installed Continuum and am trying add a Maven 2.0 project, but am getting an Unknown error trying to build POM. Not sure why. Just glancing at it, I don't see a scm element, which will be required. I assume you're seeing that error on a Continuum web page. Is there anything interesting in the log file around the same time? -- Wendy
Re: PDE Plugin
amit kumar wrote: With the help of people here especially Graham, I am able to build the plug in successfully using pde-maven-plugin. The only thing left now is that I want to package the lib folder along with the plugin, which I can do by using copy-dependency but I am not able the lib entries to Manifest file thus leaving the plug in handicapped at run time. The manifest entries tell plug in to expect the dependencies in the root folder of plugin, while I want to package it in lib folder(the tidier option). Tell the dependency plugin to copy the dependencies into the root folder, not the lib folder. Full instructions on how to do that are here: http://maven.apache.org/plugins/maven-eclipse-plugin/pde.html Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Re: What format is recommended for documentation when using mvn site ?
Hi all, Thanks for the input. I've browsed the net, and checked the supplied links too, and I think my conclusion on this issue is that this is an area still not very well covered in Maven2. I think I'll have a look at the Doxia plugin, to try to keep as Maven2 standardized as possible for now. I see that DocBook now is supported (both parser and sink) with the Doxia plugin, so I might try this first. Anyway, thank you all for the inputs! Arne I've also seen mentioned that there is work going on to create PDF from apt and xdoc. I also saw that for maven1, the xdoc format was the recomended format to use for any user specific documentation. What is the status for xdoc and Maven2 ? Do you know ? I am not the responsible of the doxia project and I don't know it too much. For the moment I use the xdoc format. I was also expecting a generated PDF output but It seems that feature is not available at the moment. But I hope that the docbook format and plugin will provide a good solution for this. It's will be nice if you can test it et get a feed back. I have a friend that work on it. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly plugin and project inheritance
You could attach the common descriptor as a build artifact one module, and then use the dependency plugin to pull it down to each child module. i.e. Use buildhelper-maven-plugin in rwcf-apps to attach dist.xml with a classifier of, e.g. assembly-descriptor. Now when you run mvn install or mvn deploy on rwcf-apps the descriptor will be published to the maven repository (local or remote respectively) Then in one of the modules that you want to use this common descriptor, add a dependency on the rwcf-apps with a type of assembly-descriptor, you use maven-dependency-plugin to copy the dependency to your target directory, and then your pom just directs the assembly plugin to use that descriptor. -Stephen On Thu, Feb 21, 2008 at 8:47 PM, Reto Bachmann-Gmür [EMAIL PROTECTED] wrote: Hello I'm having many projects that share some dependencies and that should be packaged the same way. So I wanted to have a parent project configuring the maven-assembly-plugin. I did this with the following in the parent pom: plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptors descriptor../rwcf-apps/src/assembly/dist.xml/descriptor /descriptors /configuration This only works when the parent is checked out in a sibling directory of the child. If one just check out a child project without checking out the parent assembly:assembly wont work. Things work using a descriptorRef but the predefined descriptors don't do what I'm looking for. Possibly ways to solve the issues might be: * have the plugin look up the descriptor from the parent rather * reference a descriptor with an http uri * include the content of descriptor directly in the pom ...but I didn't find a way to do it in any of these ways. Any suggestion on how to make it possible to check out a single child-project and being able to assemble it? If you would like to know more precisely what I'm doing, you may look at * The descriptor: https://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps/trunk/src/assembly/dist.xml * The parent pom: https://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps/trunk/pom.xml * A child pom: https://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-app-webdav/trunk/pom.xml Cheers, reto
Re: Problem with maven-dependency-plugin: copy-dependencies
amit kumar wrote: Can I modify Manifest entries along with the copy-dependencies goal in configuration? Or something like that. I want the Manifest.mf to have entries for the copied dependencies(in the specific folder). Do it the other way around - don't try and change the path in the manifest, the plugin won't let you. Change the location of where the dependency plugin puts the jars. Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Re: Create one jar including all dependencies
krishnan.1000 schrieb: Hi, I am a Maven newbie. So please forgive my ignorance. I am using Maven 2x for project and dependency management. I am creating a jar package. My project requires that the jar be deployed on a remote server. I can create a jar of all the classes. I would like to create a mega jar with all the expanded dependent jars in the generated jars. Is there a command for this or do I have to create a customized goal for this? You might like to look at this plugin: http://maven.apache.org/plugins/maven-shade-plugin/ Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Windows path length limitation
bad windows. I'll look at this issue before to release a new version of maven-scm On Thu, Feb 21, 2008 at 7:01 PM, KURT TOMETICH [EMAIL PROTECTED] wrote: I went ahead and logged an improvement to Maven SCM ( http://jira.codehaus.org/browse/SCM-368). Hopefully they will fix this so Windows users won't have to experience this shortcoming. Kurt Date: Thu, 21 Feb 2008 11:22:36 -0600 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Windows path length limitation oh interesting...You should check and see if there is an issue on this under maven SCM and if not open an issue there with this information http://jira.codehaus.org/browse/SCM jesse On Thu, Feb 21, 2008 at 11:15 AM, KURT TOMETICH [EMAIL PROTECTED] wrote: I agree its a limitation of the file system; however, if Continuum would feed Subversion an absolute path (when running svn commands) as opposed to a relative path then their would not be a 256 character limit. I tried this and it does work when I send Subversion an absolute path and it fails when I send it a relative path. I found an article about it online here: http://svn.haxx.se/users/archive-2005-02/1088.shtml. This shouldn't be a hard change to make and would allow Windows users to not have to worry about running into this problem. Kurt Date: Thu, 21 Feb 2008 10:48:08 -0600 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Windows path length limitation its a limitation of the file system...not a lot we can do about it :( On Tue, Feb 19, 2008 at 12:33 PM, KURT TOMETICH [EMAIL PROTECTED] wrote: Thanks for the quick response. That was my fall-back option, but I wasn't sure if there was just an easy way to configure it to use an absolute path. Shortening the root path length should help, but its still possible to reach the limit. Kurt Date: Tue, 19 Feb 2008 18:19:23 +0100 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Windows path length limitation Try to configure Build Output Directory and Working Directory to c:\\bd and c:\\wd Go to the configuration entry of the administration menu [1] -- Olivier [1] http://maven.apache.org/continuum/docs/1.1/administrator_guides/configuration.html 2008/2/19, KURT TOMETICH [EMAIL PROTECTED]: Is there a way to configure Continuum to checkout project from Subversion using an absolute path instead of a relative path? This would solve the path limitation issue on Windows. I ran into the problem where the path was too long and was able to verify that if I checked out the project using an absolute path it worked fine. Is this something I can configure on and end user system or does the project have to be recompiled to make this change? Kurt -- jesse mcconnell [EMAIL PROTECTED] -- jesse mcconnell [EMAIL PROTECTED]
Unable to run clover:instrument goal (License error)
Hi, I just started learning Maven 2 following the Maven book at http://www.sonatype.com/book/. There are a set of examples to be built using Maven which fail on the goal clover:instrument claiming a license expiry. I googled the error and searched in this mailing list for an answer but I could not find one. Do I need to purchase a license or is there a way to get a free one. Or am I missing some configuration details. regards, Uthpala - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unable to run clover:instrument goal (License error)
clover is a commercial tool. If you want an open source one, I suggest looking at corbertura ( http://cobertura.sourceforge.net) Jeff On Fri, Feb 22, 2008 at 10:31 AM, uthpala [EMAIL PROTECTED] wrote: Hi, I just started learning Maven 2 following the Maven book at http://www.sonatype.com/book/. There are a set of examples to be built using Maven which fail on the goal clover:instrument claiming a license expiry. I googled the error and searched in this mailing list for an answer but I could not find one. Do I need to purchase a license or is there a way to get a free one. Or am I missing some configuration details. regards, Uthpala - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com
Unable to run clover:instrument goal (License error)
Hi, I just started learning Maven 2 following the Maven book at http://www.sonatype.com/book/. There are a set of examples to be built using Maven which fail on the goal clover:instrument claiming a license expiry. I googled the error and searched in this mailing list for an answer but I could not find one. Do I need to purchase a license or is there a way to get a free one. Or am I missing some configuration details. regards, Uthpala - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: running a single integration test during integration-test-phase
You need to configure the Maven surefire plugin in your POM and set the test configuration property for it. Here is a sample: project [...] build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration testMyIntegrationTest/test /configuration /plugin /plugins /build [...] /project Jeff On Thu, Feb 21, 2008 at 6:26 PM, David Siefert [EMAIL PROTECTED] wrote: Hello, Is there a way to configure a POM to run a single test during the integration-test-phase via command line? ie, mvn verify -Dtest=MyIntegrationTest That way I can do the necessary build work in pre-integration-test to prepare to run the integration-test phase. Thanks, David -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com
RE: Newbie: how to do a release?
Another option is to go one step further and let maven generate the shell script(s) for you as well. Check out appassembler-maven-plugin. -Dave -Original Message- From: Upul Godage [mailto:[EMAIL PROTECTED] Sent: Thursday, February 21, 2008 11:13 PM To: Maven Users List Subject: Re: Newbie: how to do a release? Hi, Check out the assembly plugin. It does just that. You have to write an assembly descriptor xml to customize the release the way you want it. http://maven.apache.org/plugins/maven-assembly-plugin/howto.html Here is a very simple assembly descriptor file which bundles all jar files to the a lib folder and copy a given run script to the root of the distribution. assembly idbin/id includeBaseDirectorytrue/includeBaseDirectory formats formatzip/format /formats fileSets fileSet directorysrc/main/bin/directory outputDirectory//outputDirectory includes includerun.sh/include /includes fileMode755/fileMode /fileSet /fileSets dependencySets dependencySet outputDirectorylib/outputDirectory /dependencySet /dependencySets /assembly Descriptor file can be given in the pom.xml directly like this without giving it in the command line. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.1/version configuration descriptors descriptorsrc/main/assembly/bin.xml/descriptor /descriptors /configuration /plugin Hope this helps. Upul On Fri, Feb 22, 2008 at 9:26 AM, Chris [EMAIL PROTECTED] wrote: I've got a standard Java app. I've got a pom that successfully generates a jar file, and I got it to generate some javadoc as well. Now how do I generate a standard release? In a normal app, the jar goes in a /lib folder along with all the dependencies, the javadoc in /doc/api, there's /bin folder with a startup script, and a license and readme in the root. The /target directory doesn't look at all like this. There are things there that don't belong in a released app at all, like all the separate .class files. - 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]
Re: Problem with maven-dependency-plugin: copy-dependencies
Thanks. Amit Kumar On Fri, Feb 22, 2008 at 2:30 PM, Graham Leggett [EMAIL PROTECTED] wrote: amit kumar wrote: Can I modify Manifest entries along with the copy-dependencies goal in configuration? Or something like that. I want the Manifest.mf to have entries for the copied dependencies(in the specific folder). Do it the other way around - don't try and change the path in the manifest, the plugin won't let you. Change the location of where the dependency plugin puts the jars. Regards, Graham --
Re: PDE Plugin
Copying the dependencies to the root file is what has worked till now. But the ultimate packaged plug in looks a little messy. So I was just trying to do accomplish the copying of dependency to the lib folder as an improvisation. Thanks and Regards, Amit On Fri, Feb 22, 2008 at 2:26 PM, Graham Leggett [EMAIL PROTECTED] wrote: amit kumar wrote: With the help of people here especially Graham, I am able to build the plug in successfully using pde-maven-plugin. The only thing left now is that I want to package the lib folder along with the plugin, which I can do by using copy-dependency but I am not able the lib entries to Manifest file thus leaving the plug in handicapped at run time. The manifest entries tell plug in to expect the dependencies in the root folder of plugin, while I want to package it in lib folder(the tidier option). Tell the dependency plugin to copy the dependencies into the root folder, not the lib folder. Full instructions on how to do that are here: http://maven.apache.org/plugins/maven-eclipse-plugin/pde.html Regards, Graham --
Re: PDE Plugin
amit kumar wrote: Copying the dependencies to the root file is what has worked till now. But the ultimate packaged plug in looks a little messy. So I was just trying to do accomplish the copying of dependency to the lib folder as an improvisation. The need to copy the dependencies to the root folder comes about due to an Eclipse bug - The Eclipse IDE has a feature that allows you to add links to dependencies, and the Eclipse IDE puts these in links in the root of the project. Unfortunately this linked dependencies feature is not mirrored in the ant based Eclipse PDE build code, which takes the existence of the files literally. If the files aren't physically in the root directory, then the PDE build will fail. You may also encounter this in Eclipse on it's own: your project may build and run fine from within the IDE, but when you run export your product the Eclipse build mysteriously fails. Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Problem with archetype properties
Hi All, I'm using the archetype 2.0-alpha-1 plugin to create an archetype. Following the guide, I added some requiered properties to the archetype-metadata.xml: requiredProperties requiredProperty key=projectName/ /requiredProperties But when I use the archetype, I'm not being prompted for the values, hence they are not being replaced. Am I doing anything wrong? Thanks in advance. Pablo.
Re: how to define a goal which wil depends on other goal in maven?
Your question is not precise enough. I suggest you read http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html and have a look at http://cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html regards, Stefan san84 wrote: thank u but how can i do using maven 2? plz let me know with ex [EMAIL PROTECTED] wrote: san84 schrieb: hi all, how can i define a goal which depends on other goal in my maven.xml in ant we can do it as follow like blabla ... target name=a depends =b blabla ... please let me know What is the actual problem you are trying to solve? In other words, what do a and b do, and why does b need to run first? Maven has this concept of phases that it runs through in order, with zero or more plugins attached to each phase. So to do something before some other thing, the plugins are bound to the appropriate phases. But the stuff which is set up by default covers almost all cases already... Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- best regards, Stefan Seidel software developer VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel.+49 (341) 9 60 50 07 fax.+49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PDE Plugin
Hi, But I had checked some plugins that gets shipped with eclipse (3.3) for instance org.apache.batik_1.6.0.v20061222-1222, they do have a lib folder inside them but their Manifest.mf file looks a little different, it doesn't have an entry for Bundle.classpath, rather it has mentioned many packages in Export Packages. What could be the case with that plugin? Is it because they are not using maven? or something else? Just curious. Regards, Amit On Fri, Feb 22, 2008 at 6:37 PM, Graham Leggett [EMAIL PROTECTED] wrote: amit kumar wrote: Copying the dependencies to the root file is what has worked till now. But the ultimate packaged plug in looks a little messy. So I was just trying to do accomplish the copying of dependency to the lib folder as an improvisation. The need to copy the dependencies to the root folder comes about due to an Eclipse bug - The Eclipse IDE has a feature that allows you to add links to dependencies, and the Eclipse IDE puts these in links in the root of the project. Unfortunately this linked dependencies feature is not mirrored in the ant based Eclipse PDE build code, which takes the existence of the files literally. If the files aren't physically in the root directory, then the PDE build will fail. You may also encounter this in Eclipse on it's own: your project may build and run fine from within the IDE, but when you run export your product the Eclipse build mysteriously fails. Regards, Graham --
Re: How to override POM properties from CLI
Paul Gier wrote: This seems to work ok for me. I tried it locally and my profile properties override my pom properties, and cli props defined with -D override both pom and profile properties. I tried with maven 2.0.6 and 2.0.8. Can you attach a small zipped project to a jira issue that reproduces the problem? http://jira.codehaus.org/browse/MNG-3417 -- View this message in context: http://www.nabble.com/How-to-override-POM-properties-from-CLI-tp15344487s177p15633399.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using variables in src\site\apt\index.apt - is there a default-index.apt or even inheritance?
http://picasaweb.google.com/archanaa05/MysoreTrip/photo#5006538269406644850
On Fri, Feb 22, 2008 at 1:27 PM, [EMAIL PROTECTED] wrote:
Hi,
what´s the magic behind the default Site generation ? Without specifying
anything the index.html is being generated containing
About ${project.name}
${project.description}
The index.html looks like:
...
div id=bodyColumn
div id=contentBox
div class=sectionh2About Proficio API/h2pProficio sample
application from quot;Better Builds with Mavenquot;/p/div
/div
/div
...
When I now create my own src\site\apt\index.apt File, the Default with
About and Description is gone.
a) is there a default-index.apt file I can copy and modify? A
default-site.xml I´ve found in the maven-site-plugin-version.jar
b) how can I use dynamic content in an apt File,e.g. ${project.version}
or what´s the recommended way ?
I´ve read something at
http://www.nabble.com/-M2--Insert-variables-in-xdoc-apt-files-to5366829.html#a5371135
Is that the recommended way to play around with the directories using the
filtering process?
Thanx for any hints,
Torsten
Include dependency jars in packaged jar
Hello everyone? Is there a way to include the dependency jars inside the packaged jar, like in the META-INF/lib directory? And another question, is there a way to customize the application.xmldirective library-directory ? with the ear plugin?
Re: Include dependency jars in packaged jar
2008/2/22, Thor [EMAIL PROTECTED]: Hello everyone? Is there a way to include the dependency jars inside the packaged jar, like in the META-INF/lib directory? Hi Thor, have you tried mvn assembly -DdescriptorId=jar-with-dependencies? This create a jar with all dependencies exploded into it. I have used this to create an executable jar and work good for me. Luca - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Archetype plugin - variable output folders for modules
Hi All,
is there any way to specify an output directory for a module that is
different from the source directory? For instance, I'd like a module
contained in folder template-ui to be created as ${rootArtifactId}-ui.
For what I could see, the dir property is used for both input and output
directories, so it I use the ${rootArtifactId} property it will tell me that
it can't find the input folder.
Thanks in advance.
RE: Archetype plugin - variable output folders for modules
Sure, use assembly directory:
plugin
artifactIdmaven-assembly-plugin/artifactId
version2.2-beta-1/version
configurationue
outputDirectoryC:/some/dir/out/of/source/outputDirectory
appendAssemblyIdfalse/appendAssemblyId
finalNameSOMEFINALNAME/finalName
descriptors
descriptor
path/to/assembly/descriptor/dep.xml
/descriptor
/descriptors
/configuration
/plugin
-Original Message-
From: Pablo Saavedra [mailto:[EMAIL PROTECTED]
Sent: Friday, February 22, 2008 10:32 AM
To: users@maven.apache.org
Subject: Archetype plugin - variable output folders for modules
Hi All,
is there any way to specify an output directory for a module that is
different from the source directory? For instance, I'd like a module
contained in folder template-ui to be created as ${rootArtifactId}-ui.
For what I could see, the dir property is used for both input and output
directories, so it I use the ${rootArtifactId} property it will tell me
that
it can't find the input folder.
Thanks in advance.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Archetype plugin - variable output folders for modules
Thanks EJ,
but I think we are talking about different things... I want to define a
module in the archetype-metadata.xml, like this:
module id=${rootArtifactId}-main dir=template-main
name=${rootArtifactId}-main
so the archetype plugin copy all the resources from the template-main module
into a myproject-main module in the resulting project
Thanks!
On 22/02/2008, EJ Ciramella [EMAIL PROTECTED] wrote:
Sure, use assembly directory:
plugin
artifactIdmaven-assembly-plugin/artifactId
version2.2-beta-1/version
configurationue
outputDirectoryC:/some/dir/out/of/source/outputDirectory
appendAssemblyIdfalse/appendAssemblyId
finalNameSOMEFINALNAME/finalName
descriptors
descriptor
path/to/assembly/descriptor/dep.xml
/descriptor
/descriptors
/configuration
/plugin
-Original Message-
From: Pablo Saavedra [mailto:[EMAIL PROTECTED]
Sent: Friday, February 22, 2008 10:32 AM
To: users@maven.apache.org
Subject: Archetype plugin - variable output folders for modules
Hi All,
is there any way to specify an output directory for a module that is
different from the source directory? For instance, I'd like a module
contained in folder template-ui to be created as ${rootArtifactId}-ui.
For what I could see, the dir property is used for both input and output
directories, so it I use the ${rootArtifactId} property it will tell me
that
it can't find the input folder.
Thanks in advance.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with archetype properties
My bad, it was an error in the archetype-metadata.xml... Thanks anyway. Regards. On 22/02/2008, Pablo Saavedra [EMAIL PROTECTED] wrote: Hi All, I'm using the archetype 2.0-alpha-1 plugin to create an archetype. Following the guide, I added some requiered properties to the archetype-metadata.xml: requiredProperties requiredProperty key=projectName/ /requiredProperties But when I use the archetype, I'm not being prompted for the values, hence they are not being replaced. Am I doing anything wrong? Thanks in advance. Pablo.
RE: Archetype plugin - variable output folders for modules
Ahhh - sorry, lackOfCoffeeException()
-Original Message-
From: Pablo Saavedra [mailto:[EMAIL PROTECTED]
Sent: Friday, February 22, 2008 10:44 AM
To: Maven Users List
Subject: Re: Archetype plugin - variable output folders for modules
Thanks EJ,
but I think we are talking about different things... I want to define a
module in the archetype-metadata.xml, like this:
module id=${rootArtifactId}-main dir=template-main
name=${rootArtifactId}-main
so the archetype plugin copy all the resources from the template-main
module
into a myproject-main module in the resulting project
Thanks!
On 22/02/2008, EJ Ciramella [EMAIL PROTECTED] wrote:
Sure, use assembly directory:
plugin
artifactIdmaven-assembly-plugin/artifactId
version2.2-beta-1/version
configurationue
outputDirectoryC:/some/dir/out/of/source/outputDirectory
appendAssemblyIdfalse/appendAssemblyId
finalNameSOMEFINALNAME/finalName
descriptors
descriptor
path/to/assembly/descriptor/dep.xml
/descriptor
/descriptors
/configuration
/plugin
-Original Message-
From: Pablo Saavedra [mailto:[EMAIL PROTECTED]
Sent: Friday, February 22, 2008 10:32 AM
To: users@maven.apache.org
Subject: Archetype plugin - variable output folders for modules
Hi All,
is there any way to specify an output directory for a module that is
different from the source directory? For instance, I'd like a module
contained in folder template-ui to be created as ${rootArtifactId}-ui.
For what I could see, the dir property is used for both input and
output
directories, so it I use the ${rootArtifactId} property it will tell
me
that
it can't find the input folder.
Thanks in advance.
-
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]
plugin site documentation
I am trying to get my custom plugin to generate the nice summary of goals and parameters for the web site. I have tried adding plugin:report and plugin:xdoc to the pom, during the site phase. The xml gets generated, but not into the site. Anyone have any ideas? Shouldn't plugin:report be a standard run on maven-plugin packaging? Thanks, Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Trouble compiling jsps in embedded
Hello, I have a project with an embedded tomcat instance which is supposed to be compiling some JSPs. When I run a simple unit test that fetches our index page, I get a javac compiler error in our logs. (See below, complaining that package javax.servlet is missing). I have all the needed tomcat packages (especially servlet-api) as a dependency in the pom file, so it should be on the classpath, yet the compile doesn't see it. I'm wondering if the Java compiler doesn't disect the surefirebooter jar properly? Is there anyone who has run into this or has a solution? -Josh 2008-02-21 20:13:40,251 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Javac exception Compile failed; see the compiler error output for details. The compiler output looks like this: 008-02-21 20:13:40,252 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Env: Compile: javaFileName=/Users/ jpollak/src/software/projects/mhs/trunk/ mhs-core/work/mhsEngine/kiva/distrosite//org/apache/jsp/index_jsp.java classpath=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite:/private/tmp/surefirebooter4943.jar:/ System/Library/Java/Ext ensions/CoreAudio.jar:/System/Library/Java/Extensions/dns_sd.jar:/ System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/ Extensions/j3dcore.jar:/System /Library/Java/Extensions/j3dutils.jar:/System/Library/Java/Extensions/ jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/ Library/Java/Extensions/ libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/ System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/Java/ Extensions/libmlib_jai.j nilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/ Library/Java/Extensions/libShark.jnilib:/System/Library/Java/ Extensions/mlibwrapper_jai.jar:/Sy stem/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/ Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/ System/Library/Frameworks/Jav aVM.framework/Versions/1.5.0/Home/lib/ext/apple_provider.jar:/System/ Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/ dnsns.jar:/System/Library/Fr ameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/localedata.jar:/ System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/ sunjce_provider.jar: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ ext/sunpkcs11.jar cp=/opt/maven/boot/classworlds-1.1.jar cp=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/work/ mhsEngine/kiva/distrosite cp=/private/tmp/surefirebooter4943.jar cp=/System/Library/Java/Extensions/CoreAudio.jar cp=/System/Library/Java/Extensions/dns_sd.jar cp=/System/Library/Java/Extensions/j3daudio.jar cp=/System/Library/Java/Extensions/j3dcore.jar cp=/System/Library/Java/Extensions/j3dutils.jar cp=/System/Library/Java/Extensions/jai_codec.jar cp=/System/Library/Java/Extensions/jai_core.jar cp=/System/Library/Java/Extensions/libJ3D.jnilib cp=/System/Library/Java/Extensions/libJ3DAudio.jnilib cp=/System/Library/Java/Extensions/libJ3DUtils.jnilib cp=/System/Library/Java/Extensions/libmlib_jai.jnilib cp=/System/Library/Java/Extensions/libQTJNative.jnilib cp=/System/Library/Java/Extensions/libShark.jnilib cp=/System/Library/Java/Extensions/mlibwrapper_jai.jar cp=/System/Library/Java/Extensions/MRJToolkit.jar cp=/System/Library/Java/Extensions/QTJava.zip cp=/System/Library/Java/Extensions/vecmath.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/apple_provider.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/dnsns.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/localedata.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/sunjce_provider.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/sunpkcs11.jar work dir=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite extension dir=/Library/Java/Extensions:/System/Library/Java/ Extensions:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext srcDir=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite compilerTargetVM=1.5 compilerSourceVM=1.5 include=org/apache/jsp/index_jsp.java 2008-02-21 20:13:40,253 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Error compiling file: /Users/jpollak/ src/software/projects/mhs/trunk/mhs-c ore/work/mhsEngine/kiva/distrosite//org/apache/jsp/index_jsp.java [javac] Compiling 1 source file /Users/jpollak/src/software/projects/mhs/trunk/mhs-core/work/mhsEngine/ kiva/distrosite/org/apache/jsp/index_jsp.java:3: package javax.servlet does not exist import javax.servlet.*; ^
Re: Test results in shell project
I need the same thing for MbUnit based reports Wim, if you make any progress, let me know and maybe we can collaborate. I just dump out in the output Test Results are here: http://xx Eric On Feb 21, 2008, at 5:43 AM, Emmanuel Venisse wrote: Hmm, good question :) if you use a JUnit xml file, stored under target/surefire-reports/, it should work. I don't think we test the project type. In a future Continuum version, you'll can add your own plugin to do that without to create a JUnit xml file. Emmanuel On Thu, Feb 21, 2008 at 9:49 AM, Wim Heirman [EMAIL PROTECTED] wrote: Hi, I would like to include the building and testing of a Python project into Continuum. I can build the project fine as a Shell project, but is there any way to have Continuum recognize the test results? Is it enough to write out a jUnit-style XML file in the build directory somewhere that Continuum can pick up, or is there more too it? Thanks, Wim. -- ir. Wim Heirman, ELIS Department, Ghent University, Belgium Phone: +32-9-264.95.27 E-mail: [EMAIL PROTECTED] http://www.elis.UGent.be/~wheirman/http://www.elis.UGent.be/%7Ewheirman/ - Eric Pugh | Principal | OpenSource Connections, LLC | 434.466.1467 | http://www.opensourceconnections.com
webstart plugin debug output
Can anyone tell me how I can turn off the [debug] output from the webstart plugin? Didn't see anything in the docs about it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trouble compiling jsps in embedded
Is there a reason you're sending this message again when I replied to it yesterday, rather than just replying to that message to continue the thread? I'll readily admit that I didn't really give you an answer, but its not polite to send the same message again so quickly, especially without responding to the other thread first. Wayne On 2/22/08, Joshua Pollak [EMAIL PROTECTED] wrote: Hello, I have a project with an embedded tomcat instance which is supposed to be compiling some JSPs. When I run a simple unit test that fetches our index page, I get a javac compiler error in our logs. (See below, complaining that package javax.servlet is missing). I have all the needed tomcat packages (especially servlet-api) as a dependency in the pom file, so it should be on the classpath, yet the compile doesn't see it. I'm wondering if the Java compiler doesn't disect the surefirebooter jar properly? Is there anyone who has run into this or has a solution? -Josh 2008-02-21 20:13:40,251 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Javac exception Compile failed; see the compiler error output for details. The compiler output looks like this: 008-02-21 20:13:40,252 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Env: Compile: javaFileName=/Users/ jpollak/src/software/projects/mhs/trunk/ mhs-core/work/mhsEngine/kiva/distrosite//org/apache/jsp/index_jsp.java classpath=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite:/private/tmp/surefirebooter4943.jar:/ System/Library/Java/Ext ensions/CoreAudio.jar:/System/Library/Java/Extensions/dns_sd.jar:/ System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/ Extensions/j3dcore.jar:/System /Library/Java/Extensions/j3dutils.jar:/System/Library/Java/Extensions/ jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/ Library/Java/Extensions/ libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/ System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/Java/ Extensions/libmlib_jai.j nilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/ Library/Java/Extensions/libShark.jnilib:/System/Library/Java/ Extensions/mlibwrapper_jai.jar:/Sy stem/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/ Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/ System/Library/Frameworks/Jav aVM.framework/Versions/1.5.0/Home/lib/ext/apple_provider.jar:/System/ Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/ dnsns.jar:/System/Library/Fr ameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/localedata.jar:/ System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/ sunjce_provider.jar: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ ext/sunpkcs11.jar cp=/opt/maven/boot/classworlds-1.1.jar cp=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/work/ mhsEngine/kiva/distrosite cp=/private/tmp/surefirebooter4943.jar cp=/System/Library/Java/Extensions/CoreAudio.jar cp=/System/Library/Java/Extensions/dns_sd.jar cp=/System/Library/Java/Extensions/j3daudio.jar cp=/System/Library/Java/Extensions/j3dcore.jar cp=/System/Library/Java/Extensions/j3dutils.jar cp=/System/Library/Java/Extensions/jai_codec.jar cp=/System/Library/Java/Extensions/jai_core.jar cp=/System/Library/Java/Extensions/libJ3D.jnilib cp=/System/Library/Java/Extensions/libJ3DAudio.jnilib cp=/System/Library/Java/Extensions/libJ3DUtils.jnilib cp=/System/Library/Java/Extensions/libmlib_jai.jnilib cp=/System/Library/Java/Extensions/libQTJNative.jnilib cp=/System/Library/Java/Extensions/libShark.jnilib cp=/System/Library/Java/Extensions/mlibwrapper_jai.jar cp=/System/Library/Java/Extensions/MRJToolkit.jar cp=/System/Library/Java/Extensions/QTJava.zip cp=/System/Library/Java/Extensions/vecmath.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/apple_provider.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/dnsns.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/localedata.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/sunjce_provider.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/sunpkcs11.jar work dir=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite extension dir=/Library/Java/Extensions:/System/Library/Java/ Extensions:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext srcDir=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite compilerTargetVM=1.5 compilerSourceVM=1.5 include=org/apache/jsp/index_jsp.java 2008-02-21 20:13:40,253 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler -
Re: Trouble compiling jsps in embedded
Wayne, I apologize, something must have been wrong with my subscription, because neither my post, nor your reply (or any of the other messages posted yesterday) were showing up in my mailbox. I checked the online archive (mail-archives.apache.org) to see if it was something wrong on my end (mail filter, etc), and I couldn't find my message, so I assumed it had been silently canned by the mailing list. I re- subscribed to the list and reposted. Again, I apologize for sending the message, but I wasn't received list messages, and for some reason I am now. Now I see my original post on mail-archive.com, I guess I should have checked there first. In response to your original suggestions: You could try adding the servlet-api artifact as a dependency to surefire, that might do it. I'm not sure how to go about doing that... do you mean modifying surefire's own pom? Could you perhaps compile the JSPs with jspc-maven-plugin instead of asking Tomcat to do it? I don't know that its an ideal solution, but we've been using j-m-p for a while very successfully. Well, I'll admit I'm not a jsp expert, but were running embedded tomcat and not using a war, just a directory of jsps. I looked at the jspc plugin, but I'm a bit confused about how it would integrate into our system. I'll take a look. -Josh On Feb 22, 2008, at 11:33 AM, Wayne Fay wrote: Is there a reason you're sending this message again when I replied to it yesterday, rather than just replying to that message to continue the thread? I'll readily admit that I didn't really give you an answer, but its not polite to send the same message again so quickly, especially without responding to the other thread first. Wayne On 2/22/08, Joshua Pollak [EMAIL PROTECTED] wrote: Hello, I have a project with an embedded tomcat instance which is supposed to be compiling some JSPs. When I run a simple unit test that fetches our index page, I get a javac compiler error in our logs. (See below, complaining that package javax.servlet is missing). I have all the needed tomcat packages (especially servlet-api) as a dependency in the pom file, so it should be on the classpath, yet the compile doesn't see it. I'm wondering if the Java compiler doesn't disect the surefirebooter jar properly? Is there anyone who has run into this or has a solution? -Josh 2008-02-21 20:13:40,251 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Javac exception Compile failed; see the compiler error output for details. The compiler output looks like this: 008-02-21 20:13:40,252 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Env: Compile: javaFileName=/Users/ jpollak/src/software/projects/mhs/trunk/ mhs-core/work/mhsEngine/kiva/distrosite//org/apache/jsp/ index_jsp.java classpath=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite:/private/tmp/surefirebooter4943.jar:/ System/Library/Java/Ext ensions/CoreAudio.jar:/System/Library/Java/Extensions/dns_sd.jar:/ System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/ Extensions/j3dcore.jar:/System /Library/Java/Extensions/j3dutils.jar:/System/Library/Java/ Extensions/ jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/ Library/Java/Extensions/ libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/ System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/ Java/ Extensions/libmlib_jai.j nilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/ Library/Java/Extensions/libShark.jnilib:/System/Library/Java/ Extensions/mlibwrapper_jai.jar:/Sy stem/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/ Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/ System/Library/Frameworks/Jav aVM.framework/Versions/1.5.0/Home/lib/ext/apple_provider.jar:/System/ Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/ dnsns.jar:/System/Library/Fr ameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/ localedata.jar:/ System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ ext/ sunjce_provider.jar: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ ext/sunpkcs11.jar cp=/opt/maven/boot/classworlds-1.1.jar cp=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/work/ mhsEngine/kiva/distrosite cp=/private/tmp/surefirebooter4943.jar cp=/System/Library/Java/Extensions/CoreAudio.jar cp=/System/Library/Java/Extensions/dns_sd.jar cp=/System/Library/Java/Extensions/j3daudio.jar cp=/System/Library/Java/Extensions/j3dcore.jar cp=/System/Library/Java/Extensions/j3dutils.jar cp=/System/Library/Java/Extensions/jai_codec.jar cp=/System/Library/Java/Extensions/jai_core.jar cp=/System/Library/Java/Extensions/libJ3D.jnilib cp=/System/Library/Java/Extensions/libJ3DAudio.jnilib cp=/System/Library/Java/Extensions/libJ3DUtils.jnilib cp=/System/Library/Java/Extensions/libmlib_jai.jnilib
Re: assembly plugin and project inheritance
Thanks Stephen,
trying to follow the path you describe I added the following to the
parent-pom:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuild-helper-maven-plugin/artifactId
executions
execution
idattach-artifacts/id
phasepackage/phase
goals
goalattach-artifact/goal
/goals
configuration
artifacts
artifact
filesrc/assembly/dist.xml/file
typexml/type
classifier
assembly-descriptor
/classifier
/artifact
/artifacts
/configuration
/execution
/executions
/plugin
and
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
configuration
artifactItems
artifactItem
groupIdorg.wymiwyg.rwcf/groupId
artifactIdrwcf-apps/artifactId
version0.0.1/version
typexml/type
classifierassembly-descriptor/classifier
overWritefalse/overWrite
outputDirectory
${project.build.directory}/src/assembly/
/outputDirectory
destFileNamedist.xml/destFileName
/artifactItem
/artifactItems
/configuration
/plugin
furthermore I changed the descriptor of maven-assembly-plugin to use
${project.build.directory}/src/assembly/dist.xml. I didn't change
anything to the child-projects.
I can now execute mvn clean dependency:copy assembly:assembly for
child projects to create a distribution-package.
The only thing which I'm still insecure is about attaching this to
phases, the difficulty seems that the super project doesn't need to have
this attached to any phase, and the dependency resolution fails unless
executed after install (a solution might be to split the parent into a
grand-parent providing the assembly descriptor and binding it to phases
in the intermediate parent). But I'm not sure anyway in which phase to
best create zip and tar.
Cheers,
reto
Stephen Connolly wrote:
You could attach the common descriptor as a build artifact one module, and
then use the dependency plugin to pull it down to each child module.
i.e.
Use buildhelper-maven-plugin in rwcf-apps to attach dist.xml with a
classifier of, e.g. assembly-descriptor.
Now when you run mvn install or mvn deploy on rwcf-apps the descriptor will
be published to the maven repository (local or remote respectively)
Then in one of the modules that you want to use this common descriptor, add
a dependency on the rwcf-apps with a type of assembly-descriptor, you use
maven-dependency-plugin to copy the dependency to your target directory, and
then your pom just directs the assembly plugin to use that descriptor.
-Stephen
On Thu, Feb 21, 2008 at 8:47 PM, Reto Bachmann-Gmür [EMAIL PROTECTED] wrote:
Hello
I'm having many projects that share some dependencies and that should be
packaged the same way. So I wanted to have a parent project configuring
the maven-assembly-plugin.
I did this with the following in the parent pom:
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptors
descriptor../rwcf-apps/src/assembly/dist.xml/descriptor
/descriptors
/configuration
This only works when the parent is checked out in a sibling directory of
the child. If one just check out a child project without checking out
the parent assembly:assembly wont work. Things work using a
descriptorRef but the predefined descriptors don't do what I'm looking
for.
Possibly ways to solve the issues might be:
* have the plugin look up the descriptor from the parent rather
* reference a descriptor with an http uri
* include the content of descriptor directly in the pom
...but I didn't find a way to do it in any of these ways.
Any suggestion on how to make it possible to check out a single
child-project and being able to assemble it?
If you would like to know more precisely what I'm doing, you may look at
* The descriptor:
https://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps/trunk/src/assembly/dist.xml
* The parent pom:
https://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps/trunk/pom.xml
* A child pom:
war libraries scope
Does anyone know what scope is used to bring jars in the WEB-INF/lib directory of a war? It appears to bring in all scope=compile dependencies. Shouldn't this be just runtime dependencies? For example, I am precompiling all my JSPs, so I don't need jasper-compiler library. According to dependency:tree, its compile scope. But its still in my WEB-INF lib. And because of it, so is ant-1.6.5.jar Any ideas how to get rid of these? Thanks, Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: war libraries scope
On Fri, Feb 22, 2008 at 9:50 AM, Ben Tatham [EMAIL PROTECTED] wrote: Does anyone know what scope is used to bring jars in the WEB-INF/lib directory of a war? It appears to bring in all scope=compile dependencies. Shouldn't this be just runtime dependencies? For example, I am precompiling all my JSPs, so I don't need jasper-compiler library. According to dependency:tree, its compile scope. But its still in my WEB-INF lib. And because of it, so is ant-1.6.5.jar What does the pom look like? It's unusual that something like jasper-compiler (or servlet-api) would show up in the webapp. If you are declaring those dependencies, use scopeprovided/scope so Maven knows they will be provided by the container and not to include them. Be sure to 'mvn clean' after you change the pom, or things under target may be left over from previous builds and confuse the issue. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trouble compiling jsps in embedded
Its ok, you don't need to go overboard apologizing, I just want to make sure you saw my initial response. ;-) For the first issue, I was simply suggesting: build plugins plugin (surefire group, artifact, version) configurations/ executions/ dependencies dependency (servlet-api, etc) /dep /deps, plugin, plugins, build For the second issue, I imagine you could perhaps tell the embedded Tomcat to use the compiled classes in /target/_pages (the default) instead of the JSPs. But obviously you should first try to figure out why the JSPs won't compile with the embedded Tomcat, that might be easiest for you. Wayne On 2/22/08, Joshua Pollak [EMAIL PROTECTED] wrote: Wayne, I apologize, something must have been wrong with my subscription, because neither my post, nor your reply (or any of the other messages posted yesterday) were showing up in my mailbox. I checked the online archive (mail-archives.apache.org) to see if it was something wrong on my end (mail filter, etc), and I couldn't find my message, so I assumed it had been silently canned by the mailing list. I re- subscribed to the list and reposted. Again, I apologize for sending the message, but I wasn't received list messages, and for some reason I am now. Now I see my original post on mail-archive.com, I guess I should have checked there first. In response to your original suggestions: You could try adding the servlet-api artifact as a dependency to surefire, that might do it. I'm not sure how to go about doing that... do you mean modifying surefire's own pom? Could you perhaps compile the JSPs with jspc-maven-plugin instead of asking Tomcat to do it? I don't know that its an ideal solution, but we've been using j-m-p for a while very successfully. Well, I'll admit I'm not a jsp expert, but were running embedded tomcat and not using a war, just a directory of jsps. I looked at the jspc plugin, but I'm a bit confused about how it would integrate into our system. I'll take a look. -Josh On Feb 22, 2008, at 11:33 AM, Wayne Fay wrote: Is there a reason you're sending this message again when I replied to it yesterday, rather than just replying to that message to continue the thread? I'll readily admit that I didn't really give you an answer, but its not polite to send the same message again so quickly, especially without responding to the other thread first. Wayne On 2/22/08, Joshua Pollak [EMAIL PROTECTED] wrote: Hello, I have a project with an embedded tomcat instance which is supposed to be compiling some JSPs. When I run a simple unit test that fetches our index page, I get a javac compiler error in our logs. (See below, complaining that package javax.servlet is missing). I have all the needed tomcat packages (especially servlet-api) as a dependency in the pom file, so it should be on the classpath, yet the compile doesn't see it. I'm wondering if the Java compiler doesn't disect the surefirebooter jar properly? Is there anyone who has run into this or has a solution? -Josh 2008-02-21 20:13:40,251 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Javac exception Compile failed; see the compiler error output for details. The compiler output looks like this: 008-02-21 20:13:40,252 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Env: Compile: javaFileName=/Users/ jpollak/src/software/projects/mhs/trunk/ mhs-core/work/mhsEngine/kiva/distrosite//org/apache/jsp/ index_jsp.java classpath=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite:/private/tmp/surefirebooter4943.jar:/ System/Library/Java/Ext ensions/CoreAudio.jar:/System/Library/Java/Extensions/dns_sd.jar:/ System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/ Extensions/j3dcore.jar:/System /Library/Java/Extensions/j3dutils.jar:/System/Library/Java/ Extensions/ jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/ Library/Java/Extensions/ libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/ System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/ Java/ Extensions/libmlib_jai.j nilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/ Library/Java/Extensions/libShark.jnilib:/System/Library/Java/ Extensions/mlibwrapper_jai.jar:/Sy stem/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/ Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/ System/Library/Frameworks/Jav aVM.framework/Versions/1.5.0/Home/lib/ext/apple_provider.jar:/System/ Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/ dnsns.jar:/System/Library/Fr ameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/ localedata.jar:/ System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ ext/ sunjce_provider.jar: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ ext/sunpkcs11.jar
Environment management - I am not sure what to call it really!
Hello, We have lots of projects in our environment which most of them are small stand alone projects with not much dependency to each other. Every project has its own maven build system ( or going to have, we are in process of migrating the build system). I am seeking a way to ensure that all of the application are using one specific version of external artifact. For example if three projects are depend on struts, I would love to have a tool/mechanism to force all of them version 1.3.8; and in case we wanted to upgrade our struts dependency, we can do it one place instead of changing all the dependencies. Any suggestion? Can Archiva give us this kind of control? regards, Arash -- You can not depend on your eyes when your imagination is out of focus.
Re: Environment management - I am not sure what to call it really!
Create one shared parent pom with a dependencyManagement section that they all inherit. Then in your project pom dependency sections, leave out the version. It will be inherited from the shared parent. Wayne On 2/22/08, Arash Bizhan zadeh [EMAIL PROTECTED] wrote: Hello, We have lots of projects in our environment which most of them are small stand alone projects with not much dependency to each other. Every project has its own maven build system ( or going to have, we are in process of migrating the build system). I am seeking a way to ensure that all of the application are using one specific version of external artifact. For example if three projects are depend on struts, I would love to have a tool/mechanism to force all of them version 1.3.8; and in case we wanted to upgrade our struts dependency, we can do it one place instead of changing all the dependencies. Any suggestion? Can Archiva give us this kind of control? regards, Arash -- You can not depend on your eyes when your imagination is out of focus. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly plugin and project inheritance
The version I posted doesn't work as the child-projects can't perform
the attach-artifact attached to the package phase.
I've now extracted the dist configuration and the attachment of it to a
separate project[1]. Having done this I also attached the copy and the
assembly goals to the compile and package phases [2].
1.
http://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps-assembly/trunk/pom.xml
2. in
http://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps/trunk/pom.xml
Reto Bachmann-Gmür wrote:
Thanks Stephen,
trying to follow the path you describe I added the following to the
parent-pom:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuild-helper-maven-plugin/artifactId
executions
execution
idattach-artifacts/id
phasepackage/phase
goals
goalattach-artifact/goal
/goals
configuration
artifacts
artifact
filesrc/assembly/dist.xml/file
typexml/type
classifier
assembly-descriptor
/classifier
/artifact
/artifacts
/configuration
/execution
/executions
/plugin
and
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
configuration
artifactItems
artifactItem
groupIdorg.wymiwyg.rwcf/groupId
artifactIdrwcf-apps/artifactId
version0.0.1/version
typexml/type
classifierassembly-descriptor/classifier
overWritefalse/overWrite
outputDirectory
${project.build.directory}/src/assembly/
/outputDirectory
destFileNamedist.xml/destFileName
/artifactItem
/artifactItems
/configuration
/plugin
furthermore I changed the descriptor of maven-assembly-plugin to use
${project.build.directory}/src/assembly/dist.xml. I didn't change
anything to the child-projects.
I can now execute mvn clean dependency:copy assembly:assembly for
child projects to create a distribution-package.
The only thing which I'm still insecure is about attaching this to
phases, the difficulty seems that the super project doesn't need to
have this attached to any phase, and the dependency resolution fails
unless executed after install (a solution might be to split the parent
into a grand-parent providing the assembly descriptor and binding it
to phases in the intermediate parent). But I'm not sure anyway in
which phase to best create zip and tar.
Cheers,
reto
Stephen Connolly wrote:
You could attach the common descriptor as a build artifact one
module, and
then use the dependency plugin to pull it down to each child module.
i.e.
Use buildhelper-maven-plugin in rwcf-apps to attach dist.xml with a
classifier of, e.g. assembly-descriptor.
Now when you run mvn install or mvn deploy on rwcf-apps the
descriptor will
be published to the maven repository (local or remote respectively)
Then in one of the modules that you want to use this common
descriptor, add
a dependency on the rwcf-apps with a type of assembly-descriptor, you
use
maven-dependency-plugin to copy the dependency to your target
directory, and
then your pom just directs the assembly plugin to use that descriptor.
-Stephen
On Thu, Feb 21, 2008 at 8:47 PM, Reto Bachmann-Gmür [EMAIL PROTECTED]
wrote:
Hello
I'm having many projects that share some dependencies and that
should be
packaged the same way. So I wanted to have a parent project configuring
the maven-assembly-plugin.
I did this with the following in the parent pom:
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptors
descriptor../rwcf-apps/src/assembly/dist.xml/descriptor
/descriptors
/configuration
This only works when the parent is checked out in a sibling
directory of
the child. If one just check out a child project without checking out
the parent assembly:assembly wont work. Things work using a
descriptorRef but the predefined descriptors don't do what I'm looking
for.
Possibly ways to solve the issues might be:
* have the plugin look up the descriptor from the parent rather
* reference a descriptor with an http uri
* include the content of descriptor
Re: Environment management - I am not sure what to call it really!
If I put dependencies there, wouldn't all projects download them even though they may not really need them? Can Archiva help us in this situation? On Fri, Feb 22, 2008 at 12:33 PM, Wayne Fay [EMAIL PROTECTED] wrote: Create one shared parent pom with a dependencyManagement section that they all inherit. Then in your project pom dependency sections, leave out the version. It will be inherited from the shared parent. Wayne On 2/22/08, Arash Bizhan zadeh [EMAIL PROTECTED] wrote: Hello, We have lots of projects in our environment which most of them are small stand alone projects with not much dependency to each other. Every project has its own maven build system ( or going to have, we are in process of migrating the build system). I am seeking a way to ensure that all of the application are using one specific version of external artifact. For example if three projects are depend on struts, I would love to have a tool/mechanism to force all of them version 1.3.8; and in case we wanted to upgrade our struts dependency, we can do it one place instead of changing all the dependencies. Any suggestion? Can Archiva give us this kind of control? regards, Arash -- You can not depend on your eyes when your imagination is out of focus. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- You can not depend on your eyes when your imagination is out of focus.
Re: Environment management - I am not sure what to call it really!
On Fri, Feb 22, 2008 at 11:51 AM, Arash Bizhan zadeh [EMAIL PROTECTED] wrote: If I put dependencies there, wouldn't all projects download them even though they may not really need them? Can Archiva help us in this situation? Wayne said dependencyManagement, not dependencies. The former is more like a suggestion to the child project-- if the child project declares a dependency and leaves out the version, it will get the version from the parent's dependencyManagement section. A child project can still override this, so you can't force the version number from the parent. Yes, Archiva can help. You can control the contents so that developers don't have access to things that are not approved. (You'll need to use mirrors, and especially mirrorOf * in settings.xml to prevent access to external repositories.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: running a single integration test during integration-test-phase
2008/2/22 Jeff MAURY [EMAIL PROTECTED]:
You need to configure the Maven surefire plugin in your POM and set the
test
configuration property for it.
Here is a sample:
project
[...]
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
testMyIntegrationTest/test
/configuration
/plugin
/plugins
/build
[...]
/project
Jeff
On Thu, Feb 21, 2008 at 6:26 PM, David Siefert
[EMAIL PROTECTED] wrote:
Hello,
Is there a way to configure a POM to run a single test during the
integration-test-phase via command line?
ie,
mvn verify -Dtest=MyIntegrationTest
That way I can do the necessary build work in pre-integration-test to
prepare to run the integration-test phase.
Thanks,
David
--
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent
Miossec (2006)
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
What system property do I use in test${???}/test to get the test name
that was specified in the -Dtest parameter?
-David
Re: assembly plugin and project inheritance
there are two sets of goals in the maven dependency plugin.
the first set are copy and unpack. you specify the artifacts inside
the plugin configuration. these are not the set you want. the set you
want are copy-dependencies (or something like that I am on my iPod so
you will have to check) with this set you add the dependency to the
pom. that will force maven to sequence things correctly for you.
the build helper plugin has a default phase, so leave that alone. I
would bind the dependency plugin to one of the generate phases
(sources or resources)
Stephen
2/22/08, Reto Bachmann-Gmür [EMAIL PROTECTED] wrote:
The version I posted doesn't work as the child-projects can't perform
the attach-artifact attached to the package phase.
I've now extracted the dist configuration and the attachment of it to a
separate project[1]. Having done this I also attached the copy and the
assembly goals to the compile and package phases [2].
1.
http://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps-assembly/trunk/pom.xml
2. in
http://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps/trunk/pom.xml
Reto Bachmann-Gmür wrote:
Thanks Stephen,
trying to follow the path you describe I added the following to the
parent-pom:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuild-helper-maven-plugin/artifactId
executions
execution
idattach-artifacts/id
phasepackage/phase
goals
goalattach-artifact/goal
/goals
configuration
artifacts
artifact
filesrc/assembly/dist.xml/file
typexml/type
classifier
assembly-descriptor
/classifier
/artifact
/artifacts
/configuration
/execution
/executions
/plugin
and
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
configuration
artifactItems
artifactItem
groupIdorg.wymiwyg.rwcf/groupId
artifactIdrwcf-apps/artifactId
version0.0.1/version
typexml/type
classifierassembly-descriptor/classifier
overWritefalse/overWrite
outputDirectory
${project.build.directory}/src/assembly/
/outputDirectory
destFileNamedist.xml/destFileName
/artifactItem
/artifactItems
/configuration
/plugin
furthermore I changed the descriptor of maven-assembly-plugin to use
${project.build.directory}/src/assembly/dist.xml. I didn't change
anything to the child-projects.
I can now execute mvn clean dependency:copy assembly:assembly for
child projects to create a distribution-package.
The only thing which I'm still insecure is about attaching this to
phases, the difficulty seems that the super project doesn't need to
have this attached to any phase, and the dependency resolution fails
unless executed after install (a solution might be to split the parent
into a grand-parent providing the assembly descriptor and binding it
to phases in the intermediate parent). But I'm not sure anyway in
which phase to best create zip and tar.
Cheers,
reto
Stephen Connolly wrote:
You could attach the common descriptor as a build artifact one
module, and
then use the dependency plugin to pull it down to each child module.
i.e.
Use buildhelper-maven-plugin in rwcf-apps to attach dist.xml with a
classifier of, e.g. assembly-descriptor.
Now when you run mvn install or mvn deploy on rwcf-apps the
descriptor will
be published to the maven repository (local or remote respectively)
Then in one of the modules that you want to use this common
descriptor, add
a dependency on the rwcf-apps with a type of assembly-descriptor, you
use
maven-dependency-plugin to copy the dependency to your target
directory, and
then your pom just directs the assembly plugin to use that descriptor.
-Stephen
On Thu, Feb 21, 2008 at 8:47 PM, Reto Bachmann-Gmür [EMAIL PROTECTED]
wrote:
Hello
I'm having many projects that share some dependencies and that
should be
packaged the same way. So I wanted to have a parent project configuring
the maven-assembly-plugin.
I did this with the following in the parent pom:
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptors
descriptor../rwcf-apps/src/assembly/dist.xml/descriptor
/descriptors
/configuration
This only works when the parent is checked out in a sibling
directory of
the child. If one just check out a child project without checking out
the parent assembly:assembly wont work. Things work using a
descriptorRef but the predefined descriptors don't do what I'm looking
for.
Possibly ways to solve the issues might be:
* have the plugin look up the descriptor from the parent rather
* reference a descriptor with an http uri
* include the content of descriptor directly in the pom
...but I didn't find a way to do it in any of these ways.
Any suggestion on how to make it possible to check out a single
child-project and being able to assemble it?
If you would like to know more precisely what I'm
Re: Compile issues after upgrading from Maven 2.0.6
Hi Everyone, I found the root of this problem. For some reason the ClassPath order changed in Maven 2.0.7 and Maven 2.0.8 and it exposed that an older version of the servlet-api code was being pulled as a dependency. In 2.0.7 and 2.0.8, the older version shows up first and causes the failure. It took me a little while to find this because the jars were not named the same. Thanks, David On Tue, Feb 5, 2008 at 10:44 AM, Wayne Fay [EMAIL PROTECTED] wrote: Create a sample project jar that demonstrates the problem and attach it to a new JIRA issue. Wayne On 2/5/08, David Williams [EMAIL PROTECTED] wrote: Hi Everyone, I have seen this twice now so I thought I would throw this out and see if anyone else had seen this problem. We have two projects that compile fine with Maven 2.0.6 that does not with Maven 2.0.7 nor Maven 2.0.8. In both cases it is a cannot find symbol error. In the first instance, the problem was the *tomcat/jsp-api/5.0.18/jsp- api-5.0.18.jar* and the *tomcat/servlet-api/5.0.18/servlet- api-5.0.18.jar*. The second instance is with the * org/apache/myfaces/core/myfaces-api/1.2.2/myfaces-api-1.2.2.jar *and* ** org/apache/myfaces/core/myfaces-impl/1.2.2/myfaces-impl-1.2.2.jar *I checked the the correct version of the jar is on the classpath and again everything works fine with Maven 2.0.6. Has anyone seen anything like this? Thanks for your help, David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Compile issues after upgrading from Maven 2.0.6
I think there's a 2.0.5 to 2.0.6 upgrade guide: http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari ng-dependencies.html Would this have prevented your issues? -Original Message- From: David Williams [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 3:15 PM To: Maven Users List Subject: Re: Compile issues after upgrading from Maven 2.0.6 Hi Everyone, I found the root of this problem. For some reason the ClassPath order changed in Maven 2.0.7 and Maven 2.0.8 and it exposed that an older version of the servlet-api code was being pulled as a dependency. In 2.0.7 and 2.0.8, the older version shows up first and causes the failure. It took me a little while to find this because the jars were not named the same. Thanks, David On Tue, Feb 5, 2008 at 10:44 AM, Wayne Fay [EMAIL PROTECTED] wrote: Create a sample project jar that demonstrates the problem and attach it to a new JIRA issue. Wayne On 2/5/08, David Williams [EMAIL PROTECTED] wrote: Hi Everyone, I have seen this twice now so I thought I would throw this out and see if anyone else had seen this problem. We have two projects that compile fine with Maven 2.0.6 that does not with Maven 2.0.7 nor Maven 2.0.8. In both cases it is a cannot find symbol error. In the first instance, the problem was the *tomcat/jsp-api/5.0.18/jsp- api-5.0.18.jar* and the *tomcat/servlet-api/5.0.18/servlet- api-5.0.18.jar*. The second instance is with the * org/apache/myfaces/core/myfaces-api/1.2.2/myfaces-api-1.2.2.jar *and* ** org/apache/myfaces/core/myfaces-impl/1.2.2/myfaces-impl-1.2.2.jar *I checked the the correct version of the jar is on the classpath and again everything works fine with Maven 2.0.6. Has anyone seen anything like this? Thanks for your help, David - 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]
buildNumber in JavaDoc and in Site
Hi there,
i'm having a little problem:
I'm working with the buildnumber PlugIn:
plugingroupIdorg.codehaus.mojo/groupIdartifactIdbuildnumber-maven-plugin/artifactId
executions
execution
phasevalidate/phase
goalsgoalcreate/goal/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
So i tried to set the doctitle of the JavaDoc Plug to get the whole
information into the resulting JavaDoc:
configuration
doctitle${project.name} ${project.version}-${buildNumber} API/doctitle
/configuration
But as result after (mvn site) i got: - null API for the
buildNumber
So has someone here an hint to solve this
The second question will be that i'm using the site plugin to create
the sitewithin the Site-Descriptor i have activated
version position=left/
and getting the version-Entry of my pom, but i can't get my
buildNumber in there ?
Does exist an solution for this?
Thanks in advance...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migrating from Maven 1 to Maven 2
[EMAIL PROTECTED] wrote: What exactly are you looking for help with? Converting the project.xml into pom.xml? Analyzing your dependencies to see what is actually needed? Something else entirely? Wayne Well, a converter from project.xml to pom.xml would be a first start, then, yes, something to analyze the depependencies, to tell me which dependencies are simply transitive dependencies - example - if I had a maven 1project with dependencies a, b, c, and this analyzer tells me that b needs c, I could realize that a needs be and b needs c - transitive. But how could I find out which dependencies are not used at all anymore? You can use the dependency-plugin for this. The following command will analyze the dependencies for your Maven 2 project and tell you what dependencies can be removed and what dependencies should be added. mvn dependency:analyze And is there a way to tell maven to just retrieve the newest version from the repo? I know there is dependencymanagement, which I am using at great extend, is there a way / shouldn't it be possible to just leave the version number, so that maven retrieves the newest version of this dependeny? As I am doing a big step anyway - moving to maven 2 - I think I could just as well do a big clean up and also update all dependencies were possible. Thanks, Stefanie -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using variables in src\site\apt\index.apt - is there a default-index.apt or even inheritance?
Have a look at the filtering section on this page:
http://maven.apache.org/plugins/maven-site-plugin/usage.html
[EMAIL PROTECTED] wrote:
Hi,
what´s the magic behind the default Site generation ? Without specifying
anything the index.html is being generated containing
About ${project.name}
${project.description}
The index.html looks like:
...
div id=bodyColumn
div id=contentBox
div class=sectionh2About Proficio API/h2pProficio sample
application from quot;Better Builds with Mavenquot;/p/div
/div
/div
...
When I now create my own src\site\apt\index.apt File, the Default with
About and Description is gone.
a) is there a default-index.apt file I can copy and modify? A
default-site.xml I´ve found in the maven-site-plugin-version.jar
b) how can I use dynamic content in an apt File,e.g. ${project.version}
or what´s the recommended way ?
I´ve read something at
http://www.nabble.com/-M2--Insert-variables-in-xdoc-apt-files-to5366829.html#a5371135
Is that the recommended way to play around with the directories using the
filtering process?
Thanx for any hints,
Torsten
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: plugin site documentation
Ben Tatham wrote: I am trying to get my custom plugin to generate the nice summary of goals and parameters for the web site. I have tried adding plugin:report and plugin:xdoc to the pom, during the site phase. The xml gets generated, but not into the site. Anyone have any ideas? Shouldn't plugin:report be a standard run on maven-plugin packaging? Thanks, Ben You just need to include the plugin plugin in the pom of your plugin like this: reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-plugin-plugin/artifactId /plugin /plugins /reporting The run 'mvn site' -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: filtering of archetype resources
Stuart McCulloch wrote: On 20/02/2008, Laurie Harper [EMAIL PROTECTED] wrote: How do I package resources in an archetype so that they don't get filtered through Velocity when the archetype is used? Currently Velocity is choking on Javascript files contained in the archetype, and I'd rather not have to modify all the Javascript files so they will pass through Velocity without error (the archetype is packaging third-party code I don't want to modify). perhaps you could try adding: #literal() to the start of the file, and: #end to the end of the file - any text between should be copied literally by Velocity That doesn't really avoid modifying the files though... and it's not clear to me that it'd help in all cases (e.g. binary file types, if Maven/Velocity isn't already smart enough to skip them, or any file where stray whitespace at the start is an issue, etc...) The 'obvious' solution I tried (w/out success) was to specify the archetype resources in the same way I would in a POM in the same situation: resources filteringfalse/filtering includes resourcesrc/main/webapp/.../resource ... but unfortunately that doesn't seem to work in archetype.xml. Any other possibilities? L. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Stage Plugin 1.0-alpha-1 Released
The Maven team is pleased to announce the first release of the Maven Stage Plugin, version 1.0-alpha-1. http://maven.apache.org/plugins/maven-stage-plugin/ This plugin assists with staging and promoting releases by allowing you to copy artifacts from one repository to another. It currently supports copying from http|https to scp urls. You can run 'mvn -up stage:copy ... ' to get the latest version of the plugin. (Nothing was closed in JIRA for this initial release, so there are no release notes.) Enjoy, -- Wendy Smoak on behalf of the Maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Directory naming in working-directory
I was looking for the same thing. Having a problem with jtest's suppressions because they do a match on the file path. My project files normally start with /foo but in Continuum its /8 for this project so no match is found. -- View this message in context: http://www.nabble.com/Directory-naming-in-working-directory-tp14294485p15642008.html Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: ANN Maven Archetype Plugin 2.0-alpha-2 -- Ref #[1MFmZ08pl56Wmmu]
Hello, Thank you for contacting NetZero. This is an automated reply and no further response will be sent. Please do not reply to this email. If you are looking for help here are some useful links: * Online NetZero Help Center: http://www.netzero.com/support * Online Billing and Account Center: https://account.netzero.net * Reset/Retrieve your Password: http://my.netzero.com/s/resetpassword * Lookup Access Numbers in your area: http://my.netzero.com/s/numbers * Contact Us: http://www.netzero.net/support/support.html Thank you for choosing NetZero. Sincerely, NetZero Customer Support - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mvn mkdir
I have an unusual situation where we are using the exec:exec plugin (we hope to change our approach later so this isn't necessary). Before we call this executable we must create an empty directory (target/foo). What is the correct maven way to do this? -- ASCII ribbon campaign: () against HTML email /\ against Microsoft attachments Information: http://www.expita.com/nomime.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: filtering of archetype resources
On 23/02/2008, Laurie Harper [EMAIL PROTECTED] wrote: Stuart McCulloch wrote: On 20/02/2008, Laurie Harper [EMAIL PROTECTED] wrote: How do I package resources in an archetype so that they don't get filtered through Velocity when the archetype is used? Currently Velocity is choking on Javascript files contained in the archetype, and I'd rather not have to modify all the Javascript files so they will pass through Velocity without error (the archetype is packaging third-party code I don't want to modify). perhaps you could try adding: #literal() to the start of the file, and: #end to the end of the file - any text between should be copied literally by Velocity That doesn't really avoid modifying the files though... and it's not clear to me that it'd help in all cases (e.g. binary file types, if Maven/Velocity isn't already smart enough to skip them, or any file where stray whitespace at the start is an issue, etc...) The 'obvious' solution I tried (w/out success) was to specify the archetype resources in the same way I would in a POM in the same situation: resources filteringfalse/filtering includes resourcesrc/main/webapp/.../resource ... but unfortunately that doesn't seem to work in archetype.xml. Any other possibilities? have you tried setting the filtered attribute for the particular resource entry, ie: resources resourcesrc/main/resources/readme.txt/resource resource filtered=falsesrc/main/resources/BINARY/resource /resources that's worked for me in the past when I want to exclude binary files from filtering L. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Cheers, Stuart
Re: mvn mkdir
use maven-antrun-plugin to mkdir at validate phase -D On Fri, Feb 22, 2008 at 6:07 PM, deckrider [EMAIL PROTECTED] wrote: I have an unusual situation where we are using the exec:exec plugin (we hope to change our approach later so this isn't necessary). Before we call this executable we must create an empty directory (target/foo). What is the correct maven way to do this? -- ASCII ribbon campaign: () against HTML email /\ against Microsoft attachments Information: http://www.expita.com/nomime.html - 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]
