scm goal uses -C option with is not MacOSx friendly
Somehow the -C option is used in the scm:prepare-release, which unfortunately is not available in the cvs shipped by default with MacOSX. See below for the result. Should I file a new entry in Jira ? Seb [dhcp121 xml]$ maven scm:prepare-release __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc2-SNAPSHOT Using SCM method: cvs Using CVSROOT: :pserver:[EMAIL PROTECTED]:/cvs/n3 Using module: xml Verifying no modifications are present build:start: scm:validate: scm:prepare-release: scm:cvs-prepare-release: [copy] Copying 1 file to /Users/Shared/Projects/yosemite/xml [cvs] Using cvs passfile: /Users/sebastiensahuc/.cvspass [cvs] update: invalid option -- C [cvs] Usage: cvs update [-APdflRp] [-k kopt] [-r rev|-D date] [-j rev] [cvs] [-I ign] [-W spec] [files...] [cvs] -A Reset any sticky tags/date/kopts. [cvs] -P Prune empty directories. [cvs] -d Build directories, like checkout does. [cvs] -f Force a head revision match if tag/date not found. [cvs] -l Local directory only, no recursion. [cvs] -R Process directories recursively. [cvs] -p Send updates to standard output (avoids stickiness). [cvs] -k kopt Use RCS kopt -k option on checkout. [cvs] -r rev Update using specified revision/tag (is sticky). [cvs] -D date Set date to update from (is sticky). [cvs] -j rev Merge in changes made between current revision and rev. [cvs] -I ign More files to ignore (! to reset). [cvs] -W spec Wrappers specification line. [cvs] (Specify the --help global option for a list of other help options) BUILD FAILED File.. file:/Users/sebastiensahuc/.maven/plugins/maven-scm-plugin-1.2- SNAPSHOT/plugin.jelly Element... ant:cvs Line.. 215 Column 9 cvs exited with error code 1 Command line was [Executing 'cvs' with arguments: '-d:pserver:[EMAIL PROTECTED]:/cvs/n3' '-q' 'update' '-C' 'project.xml' The ' characters around the executable and arguments are not part of the command. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: xdoc plugin
On Thu, 2004-02-19 at 23:23, Brett Porter wrote: > What version should be released with RC2? > Ok, so the deal is that the introduction of the use of the pluginVar tag will break the plugin with older versions of maven that do not use that tag. So if we are going to release rc2 with a plugin that expects the presence of the pluginVar tag then we are OK, otherwise I can simply remove the use of the pluginVar tag and use the old $PluginContext reference to get what's needed. I don't think the use of the pluginVar tag is all that recent but definitely whacks people pre rc1 I believe. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: exception running clean test goals ...
That's what I did this no later than this morning with the MAVEN-1_0-BRNCH Do you know what's happening ? plugin cache issue ? Seb On Feb 20, 2004, at 2:17 PM, Sean Kelly wrote: Here is the error with a fresh CVS update. Is there any place I could look at to fix it ? I got the same error. For me, the fix was to update to MAVEN-1_0-BRANCH. :) --Sean - 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: exception running clean test goals ...
Here is the error with a fresh CVS update. Is there any place I could look at to fix it ? I got the same error. For me, the fix was to update to MAVEN-1_0-BRANCH. :) --Sean - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
exception running clean test goals ...
Here is the error with a fresh CVS update. Is there any place I could look at to fix it ? Caused by: org.apache.maven.plugin.UnknownPluginException: Unknown plugin "maven -xdoc-plugin"ââ â Thanks, Sebastien Full stack trace: java.lang.reflect.InvocationTargetException ASTIdentifier : java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImp l.invoke(UberspectImpl.java:304) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:56) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java :106) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:8 8) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:1 23) at org.apache.commons.jelly.expression.jexl.JexlExpression.evaluate(Jexl Expression.java:115) at org.apache.commons.jelly.expression.jexl.JexlExpressionFactory$Expres sionSupportLocal.evaluate(JexlExpressionFactory.java:168) at org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse (ExpressionSupport.java:106) at org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsStrin g(ExpressionSupport.java:91) at org.apache.commons.jelly.expression.CompositeExpression.evaluateAsStr ing(CompositeExpression.java:354) at org.apache.commons.jelly.expression.CompositeExpression.evaluate(Comp ositeExpression.java:346) at org.apache.commons.jelly.tags.core.SetTag.doTag(SetTag.java:130) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at com.werken.werkz.jelly.ProjectTag.doTag(ProjectTag.java:112) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.maven.plugin.PluginManager.runScript(PluginManager.java:87 5) at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.ja va:623) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java: 558) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:304) at org.apache.maven.cli.App.doMain(App.java:490) at org.apache.maven.cli.App.main(App.java:1141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: org.apache.maven.plugin.UnknownPluginException: Unknown plugin "maven -xdoc-plugin" at org.apache.maven.plugin.PluginManager.getPluginContext(PluginManager. java:761) at org.apache.maven.project.Project.getPluginContext(Project.java:363) ... 33 more clean:clean: [delete] Deleting directory D:\Projects\cc\checkout\bpml\target clean: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SCM pluging is broken --> java.lang.ClassNotFoundException: log
Please discard my question. Just did an update this morning and it seems to work fine now. Seb On Feb 20, 2004, at 10:03 AM, Sebastien Sahuc wrote: Any idea where this issue comes from. I'm on rc2 from cvs, and never ran the scm plugin before before. the goal I tried was scm:update-project Thanks a lot, Sebas java.lang.ClassNotFoundException: log at java.net.URLClassLoader$1.run(URLClassLoader.java:199) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java: 1039) at org.apache.commons.jelly.parser.XMLParser.startElement(XMLParser.java: 647) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknow n Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDi spatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkn own Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:320) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:208) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:175) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:159) at org.apache.maven.plugin.PluginManager.loadScript(PluginManager.java: 852) at org.apache.maven.plugin.PluginManager.runScript(PluginManager.java: 869) at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java :623) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java: 558) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:304) at org.apache.maven.cli.App.doMain(App.java:490) at org.apache.maven.cli.App.main(App.java:1141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja va:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) java.lang.ClassNotFoundException: log at org.apache.commons.jelly.parser.XMLParser.createSAXException(XMLParser. java:1234) at org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java: 1044) at org.apache.commons.jelly.parser.XMLParser.startElement(XMLParser.java: 647) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknow n Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDi spatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkn own Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:320) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:208) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:175) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:159) at org.apache.maven.plugin.PluginManager.loadScript(PluginManager.java: 852) at org.apache.maven.plugin.PluginManager.runScript(PluginManager.java: 869) at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java :623) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java: 558) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:304) at org.apache.maven.cli.App.doMain(App.java:490) at org.apache.maven.cli.App.main(App.java:1141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja va:39) at sun.reflect.Delega
SCM pluging is broken --> java.lang.ClassNotFoundException: log
Any idea where this issue comes from. I'm on rc2 from cvs, and never ran the scm plugin before before. the goal I tried was scm:update-project Thanks a lot, Sebas java.lang.ClassNotFoundException: log at java.net.URLClassLoader$1.run(URLClassLoader.java:199) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java: 1039) at org.apache.commons.jelly.parser.XMLParser.startElement(XMLParser.java: 647) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDis patcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkno wn Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:320) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:208) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:175) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:159) at org.apache.maven.plugin.PluginManager.loadScript(PluginManager.java: 852) at org.apache.maven.plugin.PluginManager.runScript(PluginManager.java:869) at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 623) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java: 558) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:304) at org.apache.maven.cli.App.doMain(App.java:490) at org.apache.maven.cli.App.main(App.java:1141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) java.lang.ClassNotFoundException: log at org.apache.commons.jelly.parser.XMLParser.createSAXException(XMLParser.j ava:1234) at org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java: 1044) at org.apache.commons.jelly.parser.XMLParser.startElement(XMLParser.java: 647) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDis patcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkno wn Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:320) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:208) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:175) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:159) at org.apache.maven.plugin.PluginManager.loadScript(PluginManager.java: 852) at org.apache.maven.plugin.PluginManager.runScript(PluginManager.java:869) at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 623) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java: 558) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:304) at org.apache.maven.cli.App.doMain(App.java:490) at org.apache.maven.cli.App.main(App.java:1141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.foreh
RE: [ANN] Maven AspectWerkz plugin 1.0 released
Sorry, the link to the plugin jar at the bottom is wrong. It should be: http://www.ibiblio.org/maven/maven/plugins/maven-aspectwerkz-plugin-1.0. jar To install it with Maven 1.0 RC1 and above simply type: maven plugin:download -DgroupId=maven -DartifactId=maven-aspectwerkz-plugin -Dversion=1.0 Thanks -Vincent > -Original Message- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: 20 February 2004 18:01 > To: 'Maven Users List'; [EMAIL PROTECTED] > Subject: [ANN] Maven AspectWerkz plugin 1.0 released > > The Maven team is pleased to announce the AspectWerkz plugin 1.0 > release! > > http://maven.apache.org/reference/plugins/aspectwerkz > > The Maven AspectWerkz plugin is a plugin containing goals useful for > persons wishing to build AspectWerkz projects. > > Features in this version includes: > > o Based on AspectWerkz 0.9 > o Support for offline attribdef mode (a.k.a. self-defined aspect or > model-2) > > Note that this plugin has been tested with Maven 1.0 RC1 and Maven 1.0 > RC2. > Using it with another version of Maven is at your own risks! :-) > > You can download the Maven AspectWerkz plugin here: > http://www.ibiblio.org/maven/maven/jars/maven-aspectwerkz-plugin-1.0.jar > > Have fun! > -Vincent > > > - > 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]
pom extends
As part of our current task, we have used the project.xml functionality
to allow a sub-project to pick up the dependencies of it's parent. This
works fine while on the local file system, i.e.
${basedir}/../project.xml in the sub-project's
project.xml correctly references the parent file.
The sub-project's pom is used elsewhere in our system, in other maven
projects, by the reactor therefore the pom and its parent have been uploaded to our
remote repository and the dependent projects have the pom on their dependency list.
When other projects use this pom via the reactor, the task being run fails because the
parent
project.xml can't be referenced, giving an error that the parent pom can't be found.
Both the
parent and child poms are downloaded into the local repository. As the parent and
child poms
are in the same group they are located in the same directory in the repository making
the extend
path invalid.
We are working round this problem by altering the value in the sub-project's
tag, on the copy
in the local repository, to point to the parent pom in the same directory
(parent-pom).
This is done before using the pom in the reactor and seems to work fine.
What is the suggested solution to this problem.
Thanks,
Martin.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sar files
You could just search the archives (a few messages about this in the last 48 hours)... http://bladesys.demon.co.uk/roller/page/sradford/Weblog/20040219#maven_sar_plugin On Fri, 2004-02-20 at 13:08, Rich wrote: > Does Maven support the "sar" multiproject type? I don't see a sar plug-in, > so my guess is that it doesn't. Is this something specific to Jboss? -- Dr. Sean Radford, MBBS, MSc [EMAIL PROTECTED] http://bladesys.demon.co.uk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven AspectWerkz plugin 1.0 released
The Maven team is pleased to announce the AspectWerkz plugin 1.0 release! http://maven.apache.org/reference/plugins/aspectwerkz The Maven AspectWerkz plugin is a plugin containing goals useful for persons wishing to build AspectWerkz projects. Features in this version includes: o Based on AspectWerkz 0.9 o Support for offline attribdef mode (a.k.a. self-defined aspect or model-2) Note that this plugin has been tested with Maven 1.0 RC1 and Maven 1.0 RC2. Using it with another version of Maven is at your own risks! :-) You can download the Maven AspectWerkz plugin here: http://www.ibiblio.org/maven/maven/jars/maven-aspectwerkz-plugin-1.0.jar Have fun! -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: source for dependencies
Patrick Mueller wrote on Friday, February 20, 2004 5:24 PM: > I'm new to maven, so be gentle ... > > I love the dependency mechanism, with the repos (remote and local > shadow). But one of the ways I like to work is to pull in > the source of > a dependency, not just the binaries. Mainly from an IDE usability > point of view, so that I can get nice method completion with > javadoc comment > hovers, etc. But I also often want to look at the source to figure > out what the (*)[EMAIL PROTECTED] the library is doing in the first place. > > What do folks think about adding a new element or elements to > to allow the source to be retrieved as well or instead of > the binary? Obviously, folks would have to make their source > available to make this useful, I'm not thinking this will be all that > useful from the get-go. Well, at least in the repo some packages have aside the jars directory also a distribution and/or a source directory. But I do not know, how they are referenced from Maven, too. Regards, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
source for dependencies
I'm new to maven, so be gentle ... I love the dependency mechanism, with the repos (remote and local shadow). But one of the ways I like to work is to pull in the source of a dependency, not just the binaries. Mainly from an IDE usability point of view, so that I can get nice method completion with javadoc comment hovers, etc. But I also often want to look at the source to figure out what the (*)[EMAIL PROTECTED] the library is doing in the first place. What do folks think about adding a new element or elements to to allow the source to be retrieved as well or instead of the binary? Obviously, folks would have to make their source available to make this useful, I'm not thinking this will be all that useful from the get-go. -- Patrick Mueller [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Mbean deployment descriptors
The only way I've been successful (I've only tried once or twice) was to create a custom maven.xml goal to run jmxdoclet via ant (the xdoclet maven plugin is pretty hard to understand, much less use, from my perspective). I can send you my goal definition from my other email address/computer if you'd like... -john -Original Message- From: Rich [mailto:[EMAIL PROTECTED] Sent: Friday, February 20, 2004 10:36 AM To: Maven Users List Subject: Mbean deployment descriptors Does anyone know how to generate deployment descriptors for Mbeans? Can anyone tell me where I should look to find some docs on this? Thanks in advance. -- Rich >From his PowerBook G4 An awesome piece of engineering - 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]
Mbean deployment descriptors
Does anyone know how to generate deployment descriptors for Mbeans? Can anyone tell me where I should look to find some docs on this? Thanks in advance. -- Rich >From his PowerBook G4 An awesome piece of engineering - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Is there a NoUnit plugin
Does anyone know of a NoUnit plugin for Maven? Anyone already writing one? Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Sar files
Does Maven support the "sar" multiproject type? I don't see a sar plug-in, so my guess is that it doesn't. Is this something specific to Jboss? -- Rich >From his PowerBook G4 An awesome piece of engineering - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
proxy question?
Hi all, I'm relatively new to the wonders of Maven and 'am currently looking to see how we can leverage the power of Maevn for building and deploying our Enterprise applications. One of the things I noticed is the ability to have multiple remote repositories using the coma-separated list in the property *maven.repo.remote. *This is good as we can specify ibiblio as the fisrt repository and other internal HTTP servers for internally deployed Jars. However, this leads to a problem since our HTTP servers are behind a firewall and do not require proxy athentication, while access to the ibilio Jars must go through the proxy server. At the moment it appears that specification of *maven.proxy.username *and *maven.proxy.password* results in an all on nothing switch on/off of proxy authentication. which means that you either get your internal Jars or the ibiblio ones, but not both. Is there a way, as there is with ant's *get *function, to specify a list of *nonproxyhosts* so that proxy authentication is bypassed for certain hosts? Thanks, Donal ** This document is strictly confidential and is intended for use by the addressee unless otherwise indicated. Allied Irish Banks ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: EJB JAR Plugin
Ah! I don't want to be pedantic, but would be a better property name more meaningful? > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, February 20, 2004 11:56 AM > To: [EMAIL PROTECTED] > Subject: RE: EJB JAR Plugin > > > Hi, > > the maven.ejb.src property is used to locate the ejb-jar.xml file. > > _ __ _ _ > //\ndreas.[|-bbert(a)[|\|okia.com > `- >Andreas Ebbert > Software Design Engineer - Nokia Networks OSS > gsm: +49-177-9413928, fax: +49-211-94123988 > Heltorfer Straße 1, 40472 Düsseldorf, Germany > > > -Original Message- > > From: ext Rademacher Tobias [mailto:[EMAIL PROTECTED] > > Sent: Friday, February 20, 2004 8:25 AM > > To: '[EMAIL PROTECTED]' > > Subject: EJB JAR Plugin > > > > > > > > Hi Folks, > > > > Just a simple question. What is the the source directory of > > the EJB JAR > > Plugin for? Is there any Appserver which needs sourcefiles? > > > > Thx > > Toby > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: EJB JAR Plugin
Hi, the maven.ejb.src property is used to locate the ejb-jar.xml file. _ __ _ _ //\ndreas.[|-bbert(a)[|\|okia.com `- Andreas Ebbert Software Design Engineer - Nokia Networks OSS gsm: +49-177-9413928, fax: +49-211-94123988 Heltorfer Straße 1, 40472 Düsseldorf, Germany > -Original Message- > From: ext Rademacher Tobias [mailto:[EMAIL PROTECTED] > Sent: Friday, February 20, 2004 8:25 AM > To: '[EMAIL PROTECTED]' > Subject: EJB JAR Plugin > > > > Hi Folks, > > Just a simple question. What is the the source directory of > the EJB JAR > Plugin for? Is there any Appserver which needs sourcefiles? > > Thx > Toby > > - > 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: multiproject site generation - maven reports
I had already tried this. It didn't work. The report plugins are not being automatically invoked and as a consequence, the maven-reports page doesn't include any of them. Another detail, I have some custom navigation.xml files. I think that the aggregation problem could be due to their existence but what about the report generation issue? Hey Sebastien, are your reports being properly generated, aren't they? Can you tell me the versions you're using? Sebastien Sahuc writes: > That's not true. Our report are described in the master project.xml and > are properly inherited by the subproject when doing the multiroject:site > goal. > > That being said, I'm suspecting a cache issue. Here is what I noticed: > sometimes the site is not properly generated and aggregated, even though > the build is reported to be successful. In that case I usually perform a > multiproject:clean followed by a clean goal on the master project (b/c > the multiporject:clean wouldn't clean the aggregated target !), and then > everything works as expected. > On Feb 19, 2004, at 7:39 AM, Charles N. Harvey III wrote: > >> I had the report definitions at the bottom of the master project.xml >> thinking that it would be automatically included in each subproject. >> That didn't seem to be the case. Make sure that the list of report >> definitions is in each subproject's project.xml. >> >> You may already be doing that and I am completely wrong, but its what >> I got. :) >> >> >> Charlie >> >> >> Fabio Uechi wrote: >> >>> Hi all, >>> >>> I'm facing some problems when attempting to generate my project >>> site. >>> My project its comprised of 3 sub-projects. >>> I have a master project.xml which is extended by other 3. >>> When I execute: >>> >>> maven multiproject:site >>> >>> The reactor is properly activated and all sites are generated. >>> But it's not generating any of the maven-reports I'd defined in >>> the master pom. >>> After that I generated all reports manually: >>> >>> maven multiproject:goal -Dgoal=checkstyle >>> maven multiproject:goal -Dgoal=javadoc >>> etc.. >>> >>> And then generated the site again. >>> What I've noticed is that all generated xml are properly >>> converted to html but the the links to them are missing. >>> >>> Shouldn't the report plugins be automatically called by maven? >>> What about the links? What am I doing wrong? >>> >>> >>> Thanks in advance >>> Fabio >>> -- >>> -- >>> Get your free 15 Mb POP3 email @alexandria.cc >>> Click here -> http://www.alexandria.cc/ >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >>> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > Get your free 15 Mb POP3 email @alexandria.cc Click here -> http://www.alexandria.cc/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: setting plugin properties in maven.xml
Hi,
is there any taker for this newbie question, please?
_ __ _ _
//\ndreas.[|-bbert(a)[|\|okia.com
`-
Andreas Ebbert
Software Design Engineer - Nokia Networks OSS
gsm: +49-177-9413928, fax: +49-211-94123988
Heltorfer Straße 1, 40472 Düsseldorf, Germany
> -Original Message-
> From: ext [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 17, 2004 11:00 AM
> To: [EMAIL PROTECTED]
> Subject: setting plugin properties in maven.xml
>
>
> Hi,
>
> I've asked this question already last week, but apparently
> could not express it so clearly that the problem was understood.
>
> The problem is, that we have one directory, in which the
> sources for an ejb jar are. With these sources, for different
> ejb-jars must be created. all four ejb-jars will have the
> same sources, only different deployment descriptors.
>
> The ejb-plugin expects the ejb-jar.xml to be in the directory
> ${maven.ejb.src}. But when I set this property in the
> project.properties, I cannot change that anymore. So I tried
> setting this in the maven.xml, just before the ejb:install
> goal is called.
>
> From what I've understood from the documentation, I need to
> set this property in the context of the plugin, which is
> different from the context, in which maven.xml is executed.
>
> So i tried that:
>
>value="${pom.getPluginContext('maven-ejb-plugin').setVariable(
> 'maven.ejb.src', '${basedir}/src/deployment/ejb/jvt/')}" />
> includes="ri/jvtproject.xml"
> goals="ejb:install"
> banner="Building"
> ignoreFailures="false" />
>
>
> which gives the error:
> Unable to obtain goal [ejb:ejb] -- file:/C:/Documents and
> Settings/xxx/.maven/plugins/maven-ejb-plugin-1.1/:49:34:
> C:\USERS\xxx\workspace\ossj\ip_billing\ri\src\ejb not found.
>
> which is not surprising, since the ejb-jar is in
> C:\USERS\xxx\workspace\ossj\ip_billing\ri\src\deployment\ejb\jvt
>
> Could you please let me know, how this is supposed to work?
> Thanks a lot.
>
> _ __ _ _
> //\ndreas.[|-bbert(a)[|\|okia.com
> `-
>Andreas Ebbert
> Software Design Engineer - Nokia Networks OSS
> phone: +49-177-9413928, fax: +49-211-94123988
> Heltorfer Straße 1, 40472 Düsseldorf, Germany
>
> --
> This message is confidential. If you have received this
> message in error,
> please delete it from your system. You should not copy it for
> any purpose,
> or disclose its contents to any other person. Internet
> communications are
> not secure and therefore Nokia GmbH does not accept legal
> responsibility
> for the contents of this message as it has been transmitted
> over a public
> network. Thank you.
> Nokia GmbH, Nokia Networks is a German Company. Further information
> about the Company is available from its principal offices at
> Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the
> website at http://www.nokia.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]
RE: patterntesting plugin
Hi Matt, PatternTesting is a project I started as a proof of concept. It worked quite well! I have even used it on one business project. However, my other activities I haven't found the time to work on it since that time. It is now a dead project. I should really update the home page to mention that. Now, it's not really dead and like a phoenix it is now becoming reborn through Cactus v2 (http://blogs.codehaus.org/people/vmassol/archives/000520_cactus_v2_arch itecture_proposal.html). The main difference is that while the existing pattern checks are static, the ones in Cactus2 are dynamic (at runtime), which allows for a richer set of checks. That said, I would also be happy to relinquish the leadership on the patterntesting project to anyone wishing to continue it. Thanks -Vincent > -Original Message- > From: Smith, Matt (MAN-Corporate) [mailto:[EMAIL PROTECTED] > Sent: 20 February 2004 00:12 > To: '[EMAIL PROTECTED]' > Subject: patterntesting plugin > > Hello, > > Does anybody use http://patterntesting.sourceforge.net/ ? > > Looks like it has not been updated in a while. Any info would be > appreciated. > > thanks > > Matt > > - > 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: SNAPSHOT versions
Hi Joern, I'm pretty happy switching maven in the offline mode when developing local SNAPSHOT's. maven -o java:compile This forces maven to not download the SNAPSHOTS from the central repos. Maybe this helps you. Regards Toby > -Original Message- > From: Jörn Gebhardt [mailto:[EMAIL PROTECTED] > Sent: Friday, February 20, 2004 9:35 AM > To: [EMAIL PROTECTED] > Subject: SNAPSHOT versions > > > Hi, > > I have a question concerning SNAPSHOT versions: > > Imagine you have an project A that produces the artifact > "example-1.0-SNAPSHOT.jar" and a project B that uses this > artifact. Now you > are modifying and building project A locally on your > computer, i.e. your > local repository version of example-1.0-SNAPSHOT.jar is newer > than the one > on the central repository. > > However, when you are building project B, Maven resolves the SNAPSHOT > dependency and overrides your newer local version of the jar > with the older > one from the central repository. > > Is there a way to tell Maven that it should only download the SNAPSHOT > version from the central repository if and only if the > creation date of > central version is newer than that of the local version? Or > does there exist > another best practice how to use SNAPSHOT dependencies when you are > developing projects that depend on each other? > > Thanks in advance, > Joern > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: multiproject:artifact
-Original Message- From: Daniel Flesner [mailto:[EMAIL PROTECTED] Sent: Friday, February 20, 2004 4:04 AM To: Maven Users List Subject: multiproject:artifact >we use multiproject:artifact to build multiple components. but, for our ejb's we need to build the ejb and the client jars. >i tried adding maven.multiproject.type=ejb-client but the build errors trying to build target ejb-client:ejb-client. if you change the type to ejb it just >builds the bean jar. any workarounds here? why doesn't multiproject:artifact just build the default goal that's in maven.xml? becouse most of the project do not have it and there is no reason for that. What you can do is to use the following layout: ejb ejb-client ejb-client will have maven.multiproject.type=jar and ../ejb/src/main/java So basically the same java sources will shared by both projects and ejb-client.type = "jar" Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SNAPSHOT versions
Hi, I have a question concerning SNAPSHOT versions: Imagine you have an project A that produces the artifact "example-1.0-SNAPSHOT.jar" and a project B that uses this artifact. Now you are modifying and building project A locally on your computer, i.e. your local repository version of example-1.0-SNAPSHOT.jar is newer than the one on the central repository. However, when you are building project B, Maven resolves the SNAPSHOT dependency and overrides your newer local version of the jar with the older one from the central repository. Is there a way to tell Maven that it should only download the SNAPSHOT version from the central repository if and only if the creation date of central version is newer than that of the local version? Or does there exist another best practice how to use SNAPSHOT dependencies when you are developing projects that depend on each other? Thanks in advance, Joern
