Re: Dependency and jar name
I saw this description already and out of it my question arose. I don't wanna put version number in a jar's name so the dependent jar always has the same name. But in its manifest file the version mgight be found. The question is whether it's achievable for Maven to go so far/deep? Why I need it? If you build a spanshot version (using also SNAPSHOT versions of dpendent modules) then the current approach works fine. But if I wanna rebuild one of previous versions and I have a list of versions used then of all dependent jars? The situation may look overcomplicated since I don't know where to take those old-versioned jars from:-) To rebuild dependent jars also by taking their sources from a corresponding to the version tag? But then how to store such jars (version number is not a part of jar name) and how to distinguish btw several versions of the same jar? I saw somewhere name transformation mechanism (something abount SNAPSHOT jars renaming?). Shortly speaking, I'd like to have a system letting me build versions retroactively also. Is it possible with Maven? --- Ben Walding [EMAIL PROTECTED] wrote: -ve See http://maven.apache.org/reference/project-descriptor.html#dependencies Specifically, the jar element. Roman Rytov wrote: Does it mean that if a dependent jar doesn't conform to the pattern id.version.jar its version can't be specified? Can I, in other words, define that I wanna take myjar.jar version 1.2.3? __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com - 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] __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: entities in generated HTML from xdoc-plugin
Hi, I had a look again: If I place #160; in the JSL script, it actually gets printed out, but not as entity. What Mozilla and Camino actually disliked in the HTML was that it was written as XML. When I changed the outputmode to HTML in the plugin.jelly of the xdoc plugin, everything turned out fine. Sorry about the fuss. Thanks Kai On Thursday, June 26, 2003, at 11:16 PM, Rafal Krzewski wrote: Kai Runte wrote: Hi, maybe this is the wrong list to ask, apologies if yes. Currently I working on a site.jsl script for creating webpages in the look-and-feel of our internal website. For some obscure layout reasons I need to have a nbsp; entity in the target HTML document, but utterly failed in getting Jelly/JSL to do so. If I try the following: td width=100% height=51 background=images/bann_mid.gif nbsp; /td Maven bails out with: BUILD FAILED null:-1:-1: null Could not parse Jelly script Did you try escaping the charcter as amp; entity in the jelly source? I think it will get written as in the target document: td width=100% height=51 background=images/bann_mid.gif amp;nbsp; /td R. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Real cats don't need names. But they often get called them. Yaargeroffoutofityarbastard does nicely. Terry Pratchett - The Unadulterated Cat * * email: [EMAIL PROTECTED] * * fon +44 (0)1223 494434 fax +44 (0)1223 494468 * * EMBL Outstation - EBI (European Bioinformatics Institute) * * Wellcome Trust Genome Campus * * Hinxton, Cambridge* * CB10 1SD, United Kingdom * * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependency and jar name
Brian Ewins wrote: Project releases should have no snapshot dependencies. Since your project.xml should be under version control with the rest of your code, building an old version means getting the code /and its project.xml/ from cvs or whatever, so you know what Whoops. The paragraph above was just a snapshot...build failed ;) Roman Rytov wrote: I saw this description already and out of it my question arose. I don't wanna put version number in a jar's name so the dependent jar always has the same name. But in its manifest file the version mgight be found. The question is whether it's achievable for Maven to go so far/deep? It would be possible, but in practice being able to look at a jar and know straight away what version it is is incredibly useful - particularly to non-java-literate people like support staff. Also, you'd have to restructure remote repositories entirely to support this, eg as /groupid/type/artifactid/version/filename.jar ...because maven can't magically read inside jars on the other side of an ftp connection, and you need some way of storing jars so they don't overwrite each other. Why I need it? If you build a spanshot version (using also SNAPSHOT versions of dpendent modules) then the current approach works fine. But if I wanna rebuild one of previous versions and I have a list of versions used then of all dependent jars? If you build snapshots, or depend on snapshots, you are explicitly saying I am doing development and I don't mind that this isn't repeatable. If your builds depend on release versions of jars, you have no problem - all those jars are in your repository. The situation may look overcomplicated since I don't know where to take those old-versioned jars from:-) To rebuild dependent jars also by taking their sources from a corresponding to the version tag? But then how to store such jars (version number is not a part of jar name) and how to distinguish btw several versions of the same jar? I saw somewhere name transformation mechanism (something abount SNAPSHOT jars renaming?). That's the release plugin you're thinking of. It changes all of your snapshot dependencies to explicit dependencies on jars with timestamps as their versions (the kind you get when you do jar:install-snapshot) Shortly speaking, I'd like to have a system letting me build versions retroactively also. Is it possible with Maven? Yes, but not with snapshot dependencies, and not with maven alone - you need a version control system. All you need to do is make sure your project.xml is version controlled with the rest of your source code. If you *really* want to be able to repeat snapshot builds, you should only do builds after getting a clean copy from your version control system, and store all your projects together. Most systems support rolling back to a given date/time instead of just to a tag or label. Perhaps you are looking for a continuous integration system as well? You want something that does a clean fetch of a project from version control, including its build script, runs the build script, and potentially labels the source in version control. CruiseControl and Anthill both do this, Anthill Pro has (apparently) got maven integration. These systems should be able to repeat any of their previous builds, mainly because of how they interact with version control, not because of any special properties of maven; however without maven you'll need to keep third party jars under version control as well. -Baz - 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]
changes in a chart
hi, I would like to display the changes made on the project and its quality over the time in a graphical statistic (chart). Is there a tool which already does this, a plugin or something? Or does anybody know another not too complicated possibility? Bye. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Nightly build status report
Hi there, I've been trying to search the mailing list archive for an answer, but the archive seems to be down at the moment. I am trying to create an automatic build process, using maven, which should compile all projects during the night and report any anomalities that happens. I've found the junit tag, which might be helpful, but I don't want to run JUnit tests, I want to compile the projects. Is it possible to have maven triggering failed builds and mail out the build output using existing tag libraries? If you've already answered this kind of question thousand times, please point me to an older answer :) regards, Tobias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Nightly build status report
Hi, I use anthill to manage nightly (scheduled) build. Search archives with anthill, someone gave an example on how to intergrate maven into anthill. Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, June 27, 2003 7:54 AM To: [EMAIL PROTECTED] Subject: Nightly build status report Hi there, I've been trying to search the mailing list archive for an answer, but the archive seems to be down at the moment. I am trying to create an automatic build process, using maven, which should compile all projects during the night and report any anomalities that happens. I've found the junit tag, which might be helpful, but I don't want to run JUnit tests, I want to compile the projects. Is it possible to have maven triggering failed builds and mail out the build output using existing tag libraries? If you've already answered this kind of question thousand times, please point me to an older answer :) regards, Tobias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Skipping Junit tests
On Fri, 2003-06-27 at 10:04, Moretti, Luciano (MED) wrote: Hi- 1) is there a way to get Maven to continue if junit tests fail? Every time I try to do a dist:deploy or a jar goal when a junit test fails, the process aborts. There are some junit tests that we expect at this point to fail, but we still wish to generate the artifacts. maven.test.failure.ignore = true 2) I need a way to skip specific Junit tests. We have Hansel coverage tests that we don't want to run every time we do a build, but want to run nightly when we build our snapshot. We also expect that some of the Hansel Junit tests will fail in the nightly build, but still want to distribute the artifacts (see 1) In your unitTest/ section provide an excludes/ section. Look at Maven's own POM for an example. Thanks for the help, Luciano Moretti - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Nightly build status report
The latest version of Cruisecontrol (another OS continuous integration tool) also supports Maven goals. Brendan. -Original Message- From: Alex Liu [mailto:[EMAIL PROTECTED] Sent: 27 June 2003 14:48 To: 'Maven Users List' Subject: RE: Nightly build status report Hi, I use anthill to manage nightly (scheduled) build. Search archives with anthill, someone gave an example on how to intergrate maven into anthill. Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, June 27, 2003 7:54 AM To: [EMAIL PROTECTED] Subject: Nightly build status report Hi there, I've been trying to search the mailing list archive for an answer, but the archive seems to be down at the moment. I am trying to create an automatic build process, using maven, which should compile all projects during the night and report any anomalities that happens. I've found the junit tag, which might be helpful, but I don't want to run JUnit tests, I want to compile the projects. Is it possible to have maven triggering failed builds and mail out the build output using existing tag libraries? If you've already answered this kind of question thousand times, please point me to an older answer :) regards, Tobias - 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]
struts tlds dependency
Hello, Is there anyway to set a dependency for the struts tlds in http://www.ibiblio.org/maven/struts/tlds/ repository. I try this : dependency groupIdstruts/groupId artifactIdtlds/artifactId version1.1-rc2/version typetld/type /dependency But is there a possibility to get all the tlds file in the 1.1-rc2 version without specify it one by one ? Olivier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: struts tlds dependency
You do know that all the tlds are in the jar (under META-INF/tlds/*.tld), and should have autoregistered under your webapp? You're supposed to be able to refer to tlds in jsps like so: %@ taglib uri=http://jakarta.apache.org/struts/tags-bean; prefix=bean % ...without even registering them in your web.xml, if your JSP engine is compliant with JSP 1.2. (the URI has to match the one in the tld file in the jar). There's a decent explanation in this article: http://www.onjava.com/pub/a/onjava/2001/10/10/jsp.html?page=2 it doesnt say it there, but the spec does say it the engine should search for tlds in META-INF /and its subdirectories/, in case you think the struts setup is wrong. -Baz Olivier Lamy wrote: Hello, Is there anyway to set a dependency for the struts tlds in http://www.ibiblio.org/maven/struts/tlds/ repository. I try this : dependency groupIdstruts/groupId artifactIdtlds/artifactId version1.1-rc2/version typetld/type /dependency But is there a possibility to get all the tlds file in the 1.1-rc2 version without specify it one by one ? Olivier - 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: struts tlds dependency
Also note that Struts is a day or two away from a full 1.1 release, and on the struts-dev list they are working out the details of any iBiblio requests that need to be made. There's no tlds.jar in the 1.1rc2 release, but there's a new struts-legacy.jar which will be requested for an iBiblio deployment RSN... Joe At 16:46 +0100 6/27/03, Brian Ewins wrote: You do know that all the tlds are in the jar (under META-INF/tlds/*.tld), and should have autoregistered under your webapp? You're supposed to be able to refer to tlds in jsps like so: %@ taglib uri=http://jakarta.apache.org/struts/tags-bean; prefix=bean % ...without even registering them in your web.xml, if your JSP engine is compliant with JSP 1.2. (the URI has to match the one in the tld file in the jar). There's a decent explanation in this article: http://www.onjava.com/pub/a/onjava/2001/10/10/jsp.html?page=2 it doesnt say it there, but the spec does say it the engine should search for tlds in META-INF /and its subdirectories/, in case you think the struts setup is wrong. -Baz Olivier Lamy wrote: Hello, Is there anyway to set a dependency for the struts tlds in http://www.ibiblio.org/maven/struts/tlds/ repository. I try this : dependency groupIdstruts/groupId artifactIdtlds/artifactId version1.1-rc2/version typetld/type /dependency But is there a possibility to get all the tlds file in the 1.1-rc2 version without specify it one by one ? Olivier - 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] -- -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com If nature worked that way, the universe would crash all the time. --Jaron Lanier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Error attempting changelog report
Apologies if this is a common problem - the list archive is down so I couldn't check this out in advance: When I attempt a maven-changelog-plugin:report goal, the report is always empty and although I get a build successful message, the maven.log suggests otherwise (I have attached it). The errors are variations on the following themes: 2003-06-27 17:49:25,758 ERROR org.apache.commons.jelly.tags.ant.AntTag - Class org.apache.commons.jelly.tags.core.IfTag doesn't support the nested available element. and [EMAIL PROTECTED] Reason: java.lang.NumberFormatException: includes I have a similar problem with developer activity reports. I am using 1.0b8 Has anyone experience of this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
commons-graph
Anyone have any idea of where to get source code and/or documentation for the commons-graph module, used heavily in various Maven-connected projects, but apparently obsolete? -- Jim Dixon [EMAIL PROTECTED] tel +44 117 982 0786 mobile +44 797 373 7881 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: commons-graph
On Fri, 2003-06-27 at 13:42, Jim Dixon wrote: Anyone have any idea of where to get source code and/or documentation for the commons-graph module, used heavily in various Maven-connected projects, but apparently obsolete? Comes from the jakarta-commons-sandbox/graph2 module. -- Jim Dixon [EMAIL PROTECTED] tel +44 117 982 0786 mobile +44 797 373 7881 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
torque:jdbc
The goal torque:jdbc is having problems finding my JDBC driver. I've peeked at the plugin.jelly for Torque and it's simply trying to load the driver using Class.forName() instead of accepting a nested classpath reference from the Ant task invocation. I have the following in my project.xml: dependency idopta2k/id jarOpta2000.jar/jar properties classloaderroot/classloader classloaderroot.maven/classloader /properties /dependency .so I'm not sure what classpath it needs to be in to be found. Has anyone had a similar problem?
