RE: maven-scm-provider-starteam
On 10/18/07, Ken Turner [EMAIL PROTECTED] wrote: Sorry, I'm new to this community, but what's a JIRA and how do I file it? Dan Tran wrote on Thursday, October 18, 2007 9:58 PM: JIRA info is at maven.apache.org/scm site And you have to create an account (simply email address is enough) to see some useful functionality in JIRA. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Possible conflict with ejb and jar plugins
I think the reason he's using both plugins is that the ejb-plugin currently doesn't provide the includes/excludes configuration as the jar plugin. So the intention is not to produce two (main) artifacts from the same pom but to just to have the ejb and a ejb-client jar. What happens with this pom snippet is that the jar produced by the jar-plugin is overwritten by the jar produced by the ejb-plugin, as both produce main artifacts (with the same filename) for the project. You can try moving the jar-plugin configuration afer the ejb-plugin in your pom and see if that helps. The real solution for this of course is to support the includes/excludes configuration in the ejb plugin, too. -Tim Wayne Fay schrieb: Is there a specific reason you're building both artifacts out of the one codebase? Can you not break it into 2 separate codebases and specify one as jar and the other as ejb and then put a dependency in the ejb on the jar project, as I'm assuming the ejb needs the jar files to work (like a utility library)? This is the Maven way to do things. Of course, you can do it however you want, but I generally find it easiest to just do what Maven is expecting. Wayne On 10/18/07, Mark_E [EMAIL PROTECTED] wrote: Hi Wayne, I am actually building both a jar and ejb in the same project, here are the 2 plugins I use. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId version2.2-SNAPSHOT/version configuration excludes exclude**/handlers/**/*.*/exclude /excludes /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId executions execution idejb-client/id phasepackage/phase goals goalejb/goal /goals /execution /executions configuration ejbVersion2.1/ejbVersion generateClienttrue/generateClient archive manifest addClasspathtrue/addClasspath classpathPrefixlib/classpathPrefix /manifest /archive clientIncludes clientIncludecom/**/ejb/**/*.class/clientInclude clientIncludeMETA-INF/jboss.xml/clientInclude clientIncludeMETA-INF/ejb-jar.xml/clientInclude /clientIncludes /configuration /plugin If Maven does not like that I am build both artifacts, I may just create the EJB inside the antrun plugin, since I already have the compiled classes from the compile phase. If you have any other suggestions, that would be great. Regards, Mark Wayne Fay wrote: Are you building both a Jar and an EJB Jar in a single Maven project? Or are these 2 separate projects that have a common parent? Maven likes 1 artifact per module. Please explain your project better and/or send the poms for diagnosis. Wayne On 10/18/07, Mark_E [EMAIL PROTECTED] wrote: Hello, I am running into a strange situation with the maven-ejb-plugin and maven-jar-plugin I am performing a build, building a jar and an ejb. Seems that when I execute the ejb plugin during the package phase, it messes up the execution of the maven-jar-plugin. For example, I am using the snapshot version of the maven-jar-plugin (2.2) that contains the excludes fix. If I build both an ejb and jar in my project, it seems to override the exclude switch in the jar plugin and I get files I do not want in the jar. If I turn off the maven-ejb-plugin in my build and re-run the mvn package command, the exclude switch in the jar plugin works fine and I do not get the files I excludes from my jar. I am running version 2.1 of the EJB Plugin. Just wondering if anyone else is running into this. Maybe I am doing something wrong? I thought it might be the clientInclude switch used in the ejb plugin so I disabled this in my pom.xml but the issue still exists. I have to comment out the ejb plugin all together to get the excludes for the jar to work. Anyway, if anyone has any suggestions, I would appreciate them very much. I need to get this resolved and I would like to use the maven plugin as opposed to have to do it with Ant. Regards, Mark -- View this message in context: http://www.nabble.com/Possible-conflict-with-ejb-and-jar-plugins-tf4649756s177.html#a13283698 Sent from the Maven - Users mailing list archive at Nabble.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] -- View this message in context:
RE: DuplicateProjectException
Heinrich Nirschl wrote on Thursday, October 18, 2007 6:12 PM: On 10/18/07, Jason Nerothin [EMAIL PROTECTED] wrote: Okay, so what I mean is that I have four complilation units: Unit A has compile-time dependencies on B1 and B2 which in turn have a compile-time dependency on unit C. mvn compile tries to figure out which code to link against (B1-C or B2-C) and throws a DuplicateProjectException. Is such an arrangement possible with maven or am I missing some larger point about dependency management? The situation you describe is normally handled without any problem. In fact it is quite common that dependencies have common sub-dependencies, just think of C being a logging package for example. I don't know in which situations Maven throws a DuplicateProjectException (never saw this one myself). Its maybe easier to diagnose the problem if we see the poms. In case of a copy paste error. Copy an existing sub project, add it to the multi project build and forget to adjust the artifactId ... boom! :) - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Failure getting to codehaus?
I am getting the following failure on my builds today: [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for updates from elca-services [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for updates from codehaus snapshot repository [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for updates from Sakai Plugin Repo [INFO] artifact org.apache.maven.plugins:maven-one-plugin: checking for updates from elca-services [INFO] artifact org.apache.maven.plugins:maven-one-plugin: checking for updates from codehaus snapshot repository [WARNING] repository metadata for: 'artifact org.apache.maven.plugins:maven-one-plugin' could not be retrieved from repository: codehaus snapshot repository due to an error: Error transferring file [INFO] Repository 'codehaus snapshot repository' will be blacklisted Is anyone else seeing this? -AZ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Looking for UML Diagram Plugin
On 10/19/07, Mac-Systems [EMAIL PROTECTED] wrote: i searched a bit the www for an UML Generator Plugin. Anyone can point me whats good for Maven 2 ? Generation should run unter Linux Maschine, as i read about http://wiki.wsmoak.net/cgi-bin/wiki.pl?UMLGraph which seems to run only on Windows... I was using Windows when I wrote up the example. I just did it on OS X, haven't tried it on Linux but I imagine it should work. Here's the GraphViz download page: http://www.graphviz.org/Download..php You can take the example from the Continuum pom: http://svn.apache.org/repos/asf/maven/continuum/trunk/pom.xml And here's an example of aggregated Javadocs with UML diagrams at the package and class level: http://maven.apache.org/continuum/ref/latest/apidocs/org/apache/maven/continuum/project/builder/AbstractContinuumProjectBuilder.html (Click 'FRAMES' at the top to wander around more.) HTH, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to deploy custom archetype to all users?
Yes, that works great. It automatically downloads the latest version. Thanks much! Dave Wayne Fay wrote: Your users will need to specify -DremoteRepositories=... on the command line when they run archetype:create. They may need to specify the -DarchetypeVersion though I'm honestly not sure, you'll need to test that (without specifying a version and with an older version on your machine and a newer one in the remoteRepo, does Maven go fetch it and use it, or use the one you already have?). Here are some examples from AppFuse: http://www.appfuse.org/display/APF/AppFuse+QuickStart Wayne On 10/18/07, dhoffer [EMAIL PROTECTED] wrote: I want to create a custom archetype all our developers will use to bootstrap the artifact creation process. Installing this on my system is no problem and I can release to our corporate repo. The question is how can I get this installed on all our corporate developer's systems so it is available on the command line? Also since the version of this will change as we make modifications I want them all to have the latest version. Ideally when each developer executes this archetype on their system I want the latest version to be automatically installed for them. (I want my archetype to behave like the standard built-in ones.) How can I accomplish something like this? -- View this message in context: http://www.nabble.com/How-to-deploy-custom-archetype-to-all-users--tf4650775s177.html#a13287306 Sent from the Maven - Users mailing list archive at Nabble.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] -- View this message in context: http://www.nabble.com/How-to-deploy-custom-archetype-to-all-users--tf4650775s177.html#a13295606 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Looking for UML Diagram Plugin
Hello, i searched a bit the www for an UML Generator Plugin. Anyone can point me whats good for Maven 2 ? Generation should run unter Linux Maschine, as i read about http://wiki.wsmoak.net/cgi-bin/wiki.pl?UMLGraph which seems to run only on Windows... Thanks, Jens - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WebDav, Wagon and Digest Authentication
Does anyone have any experience setting up Wagon to publish to a DAV server with Digest authentication? I've seen posts where people said it worked, but no clues as to what they had to do. Something in the server definition in settings.xml? The default seems to be to use Basic authentication which fails on the server with an obvious message. -- View this message in context: http://www.nabble.com/WebDav%2C-Wagon-and-Digest-Authentication-tf4653580s177.html#a13295600 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: [m2] SSL certificate name does not match
Adrian,
I don't know if you have already done this or not but I wanted to tell you
anyway just in case. I have Java 1.5.0_12 installed on my machine. When it
was installed, it installed the JDK and JRE directories as listed below.
C:\jdk1.5.0_12
C:\jre1.5.0_12
I first copied the jssecacert file to the
C:\jre1.5.0_12\lib\securitydirectory but that didn't fix the problem.
I then copied the file to the
C:\jdk1.5.0_12\jre\lib\security directory and that worked. Again, this most
likely won't help but I wanted to post it just in case.
David
On 10/13/07, Adrian Herscu [EMAIL PROTECTED] wrote:
Hi David,
Thanks for your reply.
I checked that blog; however the solution described there seems to
belong to other problem:
snip
javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to
find valid certification path to requested target
[This happens] when trying to open an SSL connection to a host using
JSSE. What this usually means is that the server is using a test
certificate (possibly generated using keytool) rather than a certificate
from a well known commercial Certification Authority such as Verisign or
GoDaddy. Web browsers display warning dialogs in this case, but since
JSSE cannot assume an interactive user is present it just throws an
exception by default.
/snip
Because I am somewhat desperate, I have tested that program. It seems to
do what the standard keytool does... I copied the generated jssecacert
file into my ${jre.home}/lib/security directory and hoped for the
best... But it didn't happen :-( I checked that the file was read using
a file monitor, and it was read.
It seems that the solution could only be provided by applications (
http://java.sun.com/javase/6/docs/technotes/guides/security/jsse/JSSERefGuide.html#ciphersuitechoice
).
In this case, Maven should provide the option to override the default
host name checking algorithm with a do-nothing one.
Adrian.
David Williams wrote:
Sorry it was late when I replied. = ) Here's the link
http://blogs.sun.com/andreas/entry/no_more_unable_to_find
On 10/11/07, Adrian Herscu [EMAIL PROTECTED] wrote:
Yeah... Where is the link :-)?
I tried to play with the keytool program. I have imported the SSL
certificate into my key store; this creates a file named .keystore in
C:\Documents and Settings\me. I tried to run Maven and DAVExplorer;
their behavior did not change :-(
Now the weird things:
1. I have monitored the file access to the .keystore file. When I am
running keytool -list the .keystore file is accessed (seems like my
file
monitoring program works). When I am running Maven or DAVExplorer, the
.keystore file is not accessed at all!
2. Maven is able to upload files to my WebDAV server! If I am building
all my modules locally, then I can run mvn deploy and the files are
uploaded!!!
Adrian.
Tim Kettler wrote:
Where's the link :-)?
David Williams schrieb:
Adrian,
This link may help you. This java program allows you to manually
accept the
cert and place the generated file in your JDK or JRE. Then the java
keeps
it as an accept cert. I have not tried this with Maven but it worked
with
another application where the cert didn't match the server
name. Down
side
is that it would have to be on every user's machine.
Thanks,
David
On 10/10/07, Adrian Herscu [EMAIL PROTECTED] wrote:
Hi all,
I am hosting my project sources and binaries with some external
provider. He cannot set up an SSL certificate for my domain name...
Meanwhile, the only alternative is accept those SSL warnings about
domain name mismatch. I am getting them in my browser and also in my
SVN
client.
Now I am trying to set up Maven to build and deploy my project to
this
provider. The problem is that I am getting these messages from
Maven:
snip
[WARNING] repository metadata for: 'snapshot
org.wirexn.build.extensions:wirexn-
build-extensions:1.0-alpha-4-SNAPSHOT' could not be retrieved from
repository: s
[EMAIL PROTECTED] due to an error: Error transferring file
[INFO] Repository '[EMAIL PROTECTED]' will be blacklisted
/snip
...and the artifacts cannot be resolved (of course).
I tried to see if this is a JRE specific problem. Downloaded a
Java-based WebDAV client (DAVExplorer), and it fails to connect with
this error message:
javax.net.ssl.SSLException: Name in certificate his.domain.name
does
not match host name my.domain.name
Anyone knows about a hidden switch/option/configuration file to make
the
JRE accept the SSL connection even if the host name doesn't match to
that on the certificate?
Please help,
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Possible conflict with ejb and jar plugins
The plugins are versioned independently. I assume the exclude/include functionality is simply not available in ejb plugin v2.1. Wayne On 10/19/07, Mark_E [EMAIL PROTECTED] wrote: I think your right, somehow the excludes not working in the ejb plugin is overriding the excludes that now works in the jar plugin (2.2-SNAPSHOT). The ejb plugin is only at version 2.1 so my guess is the path that was put into the jar plugin needs to go into the ejb plugin. I will try to submit this as an issue. Regards, Mark Tim Kettler wrote: I think the reason he's using both plugins is that the ejb-plugin currently doesn't provide the includes/excludes configuration as the jar plugin. So the intention is not to produce two (main) artifacts from the same pom but to just to have the ejb and a ejb-client jar. What happens with this pom snippet is that the jar produced by the jar-plugin is overwritten by the jar produced by the ejb-plugin, as both produce main artifacts (with the same filename) for the project. You can try moving the jar-plugin configuration afer the ejb-plugin in your pom and see if that helps. The real solution for this of course is to support the includes/excludes configuration in the ejb plugin, too. -Tim Wayne Fay schrieb: Is there a specific reason you're building both artifacts out of the one codebase? Can you not break it into 2 separate codebases and specify one as jar and the other as ejb and then put a dependency in the ejb on the jar project, as I'm assuming the ejb needs the jar files to work (like a utility library)? This is the Maven way to do things. Of course, you can do it however you want, but I generally find it easiest to just do what Maven is expecting. Wayne On 10/18/07, Mark_E [EMAIL PROTECTED] wrote: Hi Wayne, I am actually building both a jar and ejb in the same project, here are the 2 plugins I use. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId version2.2-SNAPSHOT/version configuration excludes exclude**/handlers/**/*.*/exclude /excludes /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId executions execution idejb-client/id phasepackage/phase goals goalejb/goal /goals /execution /executions configuration ejbVersion2.1/ejbVersion generateClienttrue/generateClient archive manifest addClasspathtrue/addClasspath classpathPrefixlib/classpathPrefix /manifest /archive clientIncludes clientIncludecom/**/ejb/**/*.class/clientInclude clientIncludeMETA-INF/jboss.xml/clientInclude clientIncludeMETA-INF/ejb-jar.xml/clientInclude /clientIncludes /configuration /plugin If Maven does not like that I am build both artifacts, I may just create the EJB inside the antrun plugin, since I already have the compiled classes from the compile phase. If you have any other suggestions, that would be great. Regards, Mark Wayne Fay wrote: Are you building both a Jar and an EJB Jar in a single Maven project? Or are these 2 separate projects that have a common parent? Maven likes 1 artifact per module. Please explain your project better and/or send the poms for diagnosis. Wayne On 10/18/07, Mark_E [EMAIL PROTECTED] wrote: Hello, I am running into a strange situation with the maven-ejb-plugin and maven-jar-plugin I am performing a build, building a jar and an ejb. Seems that when I execute the ejb plugin during the package phase, it messes up the execution of the maven-jar-plugin. For example, I am using the snapshot version of the maven-jar-plugin (2.2) that contains the excludes fix. If I build both an ejb and jar in my project, it seems to override the exclude switch in the jar plugin and I get files I do not want in the jar. If I turn off the maven-ejb-plugin in my build and re-run the mvn package command, the exclude switch in the jar plugin works fine and I do not get the files I excludes from my jar. I am running version 2.1 of the EJB Plugin. Just wondering if anyone else is running into this. Maybe I am doing something wrong? I thought it might be the clientInclude switch used in the ejb plugin so I disabled this in my pom.xml but the issue still exists. I have to comment out the ejb plugin all together to get the excludes for the jar to work. Anyway, if anyone has any suggestions, I would appreciate them very much. I need to get this resolved and I would like to use the maven plugin
[ANN] JsUnit 1.3 final released
New release JsUnit version 1.3 Note, this is JsUnit from BerliOS, not to be mistaken with JsUnit from SourceForge. Both projects are completely independent, they went simply public nearly both at the same time years ago. JsUnit is a simple framework to write repeatable tests in JavaScript. It is an instance of the xUnit architecture for unit testing frameworks. JsUnit is a port of JUnit 3.8.1 originally written by Erich Gamma and Kent Beck. This implementation is aimed at independent scripts and was originally written for server-side JavaScript. Aside from various small improvements it includes now an XMLResultPrinter to generate XML that can be used by JUnit reporting tools. This functionality is used for the new Maven 2 plugin and Ant Task, that integrate Rhino as JavaScript engine to run JsUnit tests in a build environment. See release notes: http://jsunit.berlios.de/release.html Artifacts and plugins will be soon available at the central repository (http://jira.codehaus.org/browse/MAVENUPLOAD-1774). Enjoy! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Plugins run from package=pom project run incorrectly
I have a project in a directory called trunk. Its packaging is pom. It has a modules tag with several child projects to run. Each of those projects has its packaging as 'jar' or 'war'. So when I run 'mvn install' from the parent pom project, it goes into the first child jar project, where I must run the maven 2 javadoc plugin as part of 'mvn install' so that the javadocs are generated and so that they can be copied into the next project's War file. However from the javadoc:javadoc documentation: * Automatically executes within the lifecycle phase: |generate-sources| * Invokes the execution of the lifecycle phase |generate-sources| prior to executing itself. This fine except the invoked execution of generate-sources does not happen in the first child jar project scope, it gets run in the parent pom project's scope! So it does a generate-sources on ALL of the child projects. This is wrong. It should run in the scope of the project in whose pom file it is invoked. In this case it should run in the first child jar project's scope. We see this with most of the plugins that are run where they are not originally supposed to run. It causes a lot of problems and forces us to use 'mvn install' individually in each of the child projects.
Re: Possible conflict with ejb and jar plugins
I think your right, somehow the excludes not working in the ejb plugin is overriding the excludes that now works in the jar plugin (2.2-SNAPSHOT). The ejb plugin is only at version 2.1 so my guess is the path that was put into the jar plugin needs to go into the ejb plugin. I will try to submit this as an issue. Regards, Mark Tim Kettler wrote: I think the reason he's using both plugins is that the ejb-plugin currently doesn't provide the includes/excludes configuration as the jar plugin. So the intention is not to produce two (main) artifacts from the same pom but to just to have the ejb and a ejb-client jar. What happens with this pom snippet is that the jar produced by the jar-plugin is overwritten by the jar produced by the ejb-plugin, as both produce main artifacts (with the same filename) for the project. You can try moving the jar-plugin configuration afer the ejb-plugin in your pom and see if that helps. The real solution for this of course is to support the includes/excludes configuration in the ejb plugin, too. -Tim Wayne Fay schrieb: Is there a specific reason you're building both artifacts out of the one codebase? Can you not break it into 2 separate codebases and specify one as jar and the other as ejb and then put a dependency in the ejb on the jar project, as I'm assuming the ejb needs the jar files to work (like a utility library)? This is the Maven way to do things. Of course, you can do it however you want, but I generally find it easiest to just do what Maven is expecting. Wayne On 10/18/07, Mark_E [EMAIL PROTECTED] wrote: Hi Wayne, I am actually building both a jar and ejb in the same project, here are the 2 plugins I use. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId version2.2-SNAPSHOT/version configuration excludes exclude**/handlers/**/*.*/exclude /excludes /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId executions execution idejb-client/id phasepackage/phase goals goalejb/goal /goals /execution /executions configuration ejbVersion2.1/ejbVersion generateClienttrue/generateClient archive manifest addClasspathtrue/addClasspath classpathPrefixlib/classpathPrefix /manifest /archive clientIncludes clientIncludecom/**/ejb/**/*.class/clientInclude clientIncludeMETA-INF/jboss.xml/clientInclude clientIncludeMETA-INF/ejb-jar.xml/clientInclude /clientIncludes /configuration /plugin If Maven does not like that I am build both artifacts, I may just create the EJB inside the antrun plugin, since I already have the compiled classes from the compile phase. If you have any other suggestions, that would be great. Regards, Mark Wayne Fay wrote: Are you building both a Jar and an EJB Jar in a single Maven project? Or are these 2 separate projects that have a common parent? Maven likes 1 artifact per module. Please explain your project better and/or send the poms for diagnosis. Wayne On 10/18/07, Mark_E [EMAIL PROTECTED] wrote: Hello, I am running into a strange situation with the maven-ejb-plugin and maven-jar-plugin I am performing a build, building a jar and an ejb. Seems that when I execute the ejb plugin during the package phase, it messes up the execution of the maven-jar-plugin. For example, I am using the snapshot version of the maven-jar-plugin (2.2) that contains the excludes fix. If I build both an ejb and jar in my project, it seems to override the exclude switch in the jar plugin and I get files I do not want in the jar. If I turn off the maven-ejb-plugin in my build and re-run the mvn package command, the exclude switch in the jar plugin works fine and I do not get the files I excludes from my jar. I am running version 2.1 of the EJB Plugin. Just wondering if anyone else is running into this. Maybe I am doing something wrong? I thought it might be the clientInclude switch used in the ejb plugin so I disabled this in my pom.xml but the issue still exists. I have to comment out the ejb plugin all together to get the excludes for the jar to work. Anyway, if anyone has any suggestions, I would appreciate them very much. I need to get this resolved and I would like to use the maven plugin as opposed to have to do it with Ant. Regards, Mark -- View this message in context: http://www.nabble.com/Possible-conflict-with-ejb-and-jar-plugins-tf4649756s177.html#a13283698 Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Possible conflict with ejb and jar plugins
Hi Wayne, I am only building both artifacts out of one pom since the project itself is meant to produce a jar and an ejb that we deploy to the application server. See I currently do this with my Ant build and as I migrate over to Maven, I guess I need to get used to the Maven way of doing things. The code for both is in one subversion project so I figured it would be easier to do it together. Maybe I can define a parent pom for this and build each as a module somehow. Wayne Fay wrote: Is there a specific reason you're building both artifacts out of the one codebase? Can you not break it into 2 separate codebases and specify one as jar and the other as ejb and then put a dependency in the ejb on the jar project, as I'm assuming the ejb needs the jar files to work (like a utility library)? This is the Maven way to do things. Of course, you can do it however you want, but I generally find it easiest to just do what Maven is expecting. Wayne On 10/18/07, Mark_E [EMAIL PROTECTED] wrote: Hi Wayne, I am actually building both a jar and ejb in the same project, here are the 2 plugins I use. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId version2.2-SNAPSHOT/version configuration excludes exclude**/handlers/**/*.*/exclude /excludes /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId executions execution idejb-client/id phasepackage/phase goals goalejb/goal /goals /execution /executions configuration ejbVersion2.1/ejbVersion generateClienttrue/generateClient archive manifest addClasspathtrue/addClasspath classpathPrefixlib/classpathPrefix /manifest /archive clientIncludes clientIncludecom/**/ejb/**/*.class/clientInclude clientIncludeMETA-INF/jboss.xml/clientInclude clientIncludeMETA-INF/ejb-jar.xml/clientInclude /clientIncludes /configuration /plugin If Maven does not like that I am build both artifacts, I may just create the EJB inside the antrun plugin, since I already have the compiled classes from the compile phase. If you have any other suggestions, that would be great. Regards, Mark Wayne Fay wrote: Are you building both a Jar and an EJB Jar in a single Maven project? Or are these 2 separate projects that have a common parent? Maven likes 1 artifact per module. Please explain your project better and/or send the poms for diagnosis. Wayne On 10/18/07, Mark_E [EMAIL PROTECTED] wrote: Hello, I am running into a strange situation with the maven-ejb-plugin and maven-jar-plugin I am performing a build, building a jar and an ejb. Seems that when I execute the ejb plugin during the package phase, it messes up the execution of the maven-jar-plugin. For example, I am using the snapshot version of the maven-jar-plugin (2.2) that contains the excludes fix. If I build both an ejb and jar in my project, it seems to override the exclude switch in the jar plugin and I get files I do not want in the jar. If I turn off the maven-ejb-plugin in my build and re-run the mvn package command, the exclude switch in the jar plugin works fine and I do not get the files I excludes from my jar. I am running version 2.1 of the EJB Plugin. Just wondering if anyone else is running into this. Maybe I am doing something wrong? I thought it might be the clientInclude switch used in the ejb plugin so I disabled this in my pom.xml but the issue still exists. I have to comment out the ejb plugin all together to get the excludes for the jar to work. Anyway, if anyone has any suggestions, I would appreciate them very much. I need to get this resolved and I would like to use the maven plugin as opposed to have to do it with Ant. Regards, Mark -- View this message in context: http://www.nabble.com/Possible-conflict-with-ejb-and-jar-plugins-tf4649756s177.html#a13283698 Sent from the Maven - Users mailing list archive at Nabble.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] -- View this message in context: http://www.nabble.com/Possible-conflict-with-ejb-and-jar-plugins-tf4649756s177.html#a13284025 Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Looking for UML Diagram Plugin
On 19/10/2007, Wendy Smoak [EMAIL PROTECTED] wrote: I was using Windows when I wrote up the example. I just did it on OS X, haven't tried it on Linux but I imagine it should work. Here's the GraphViz download page: http://www.graphviz.org/Download..php You can take the example from the Continuum pom: http://svn.apache.org/repos/asf/maven/continuum/trunk/pom.xml And here's an example of aggregated Javadocs with UML diagrams at the package and class level: http://maven.apache.org/continuum/ref/latest/apidocs/org/apache/maven/continuum/project/builder/AbstractContinuumProjectBuilder.html (Click 'FRAMES' at the top to wander around more.) That's great :) Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The svn command failed ... Server certificate verification failed: issuer is not trusted
Greetings Wendy: Thanks for seeing this. I do use a startup script for continuum. It uses the environment from /etc/profile which contains this relevant info: ... JAVA_HOME=/usr/lib/jvm/java-6-sun MAVEN_HOME=/opt/maven PATH=$PATH:$MAVEN_HOME/bin JAVA_OPTS=-Xms256m -Xmx1792m -XX:PermSize=128m -XX:MaxPermSize=512m -Djava.awt.headless=true export JAVA_HOME JAVA_OPTS MAVEN_HOME ... But I can also use the environment from /etc/profile from the command line before invoking the svn checkout: [EMAIL PROTECTED]:/home/bill# su continuum $ bash [EMAIL PROTECTED]:/home/bill$ . /etc/profile [EMAIL PROTECTED]:/home/bill$ svn list https://localhost/repo/emap branches/ tags/ trunk/ [EMAIL PROTECTED]:/home/bill$ So thats where I get stuck. Does this give you any info more info to look at? Is there any other debug info I could send along? Thanks. Bill. Wendy Smoak-3 wrote: On 10/14/07, Bill Brown [EMAIL PROTECTED] wrote: This issue still exists for me. I run continuum with the user I created continuum . I am able to check out code with the continuum user from the command line. I have already manually accepted the certificate verification permenantly from the command line as the continuum user. After all of this, the build fails with the same error message as the original post. Does anyone else have another suggestion? Am I the only user experiencing this issue? It's a legitimate issue, but accepting the certificate should have fixed it. Most likely, Continuum is not running in exactly the same environment that you get when you log in. How are you starting Continuum? -- Wendy -- View this message in context: http://www.nabble.com/The-svn-command-failed-...-Server-certificate-verification-failed%3A-issuer-is-not-trusted-tf4611163.html#a13298429 Sent from the Continuum - Users mailing list archive at Nabble.com.
Assembly change artifact extension
Hi Is it possible to change assembly artifact extension (here i need to produce a SAR) ? I konw it is possible to do this for over plugins, eg: jar (Create a new empty plugin with a components.xml file with role-hintmy.new.extension/role-hint) But i fail to do this with assembly. Any ideas ? -- View this message in context: http://www.nabble.com/Assembly-change-artifact-extension-tf4654427s177.html#a13298340 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: How to compile/package files in a module into different jars?
Here are some of the negatives: Testing time increases if more files are grouped, bugs can take longer to be found if alot of files are compiled together, and the possibility of the whole application not working because the code can't find the correct files/jars. The reason why the 1 jar/module is kinda of a problem is that coders at my company right now already have their hands full, therefore trying to get them to change the code so it suites the default maven is gonna be very difficult. That is why I'm trying to get maven to work with our application without any code change. Which really means that after i figure this problem out, I also have to create a custom archetype (which i still gotta learn how to do). So ya this is some of the negatives in adding more modules to jar certain files. -- View this message in context: http://www.nabble.com/How-to-compile-package-files-in-a-module-into-different-jars--tf4654180s177.html#a13297870 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: M2 release:prepare fails with Subversion to tag SCM reason: Source url is from different repository
I got the error message Source url is from different repository a while back. It turned out that having a user name in the scm url can sometimes cause problems for the release-plugin. After I removed the user name from the scm url it worked. bmat wrote: mvn release:prepare --- I recently had this problem using a local installation of subversion and using file uris e.g. developerConnectionscm:svn:file://localhost/repostory/myproject/trunk/developerConnection I could not get this to work... so I installed Apache 2.0 (Note 2.0 NOT 2.2 cos this doesn't work with subversion apparently). Now using the following (NOTE: the trailing slash! this is important) developerConnectionscm:svn:http://localhost/svn/repository/myproject/trunk//developerConnection this works fine for me (even on windows vista! amazing!) This link was useful : http://www.codeproject.com/w2k/SubversionApache.asp; but the authentication file is wrong i think..at least it didn't work for me. If you change the recommended line from this [/] * = r [test1:/] user1 = rw user2 = [test2:/] user1 = r user2 = rw to this [test1:/myproject] user1 = rw user2 = rw it should work... it is important to specify the repository name here if SVNParentPath is specified in apache httpd.conf. I hope this saves somebody some time and hair as I've nearly pulled all mine out :-) Cheers Ben Markku Saarela wrote: Hi, We are using Maven2 2.0.4 with Subversion 1.3 and now we can't make anymore releases. Previously we success. Here is snippet from parent pom.xml scm connectionscm:svn:svn://fitst37/income/trunk/connection developerConnectionscm:svn:svn://fitst37/income/trunk/developerConnection /scm plugin artifactIdmaven-release-plugin/artifactId configuration usernamesaarfmar/username password12345/password /configuration /plugin Here is output: [INFO] [release:prepare] [INFO] Resuming release from phase 'scm-tag' [INFO] Tagging release with the label 1.0.0... [INFO] Executing: svn --non-interactive copy --file C:\DOCUME~1\saarfmar\LOCALS~1\Temp\maven-scm-108 0661760.commit . svn://fitst37/income/tags/1.0.0 [INFO] Working directory: C:\temp\income [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Source url 'svn://[EMAIL PROTECTED]/income/trunk' is from different repository [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Source url 'svn://[EMAIL PROTECTED]/income/trunk' is from different repository at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor .java:555) Anyone have any idea what do to? Regards, Markku Saarela - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Failure getting to codehaus?
Neither of the plugins listed in the log below are in the codehaus repository, they are in the central repository. It looks to me as if you have excluded the central repository and/or replaced it with elca-services and Sakai Plugin Repo. Info about repositories can be found here: http://maven.apache.org/guides/introduction/introduction-to-repositories.html Aaron Zeckoski wrote: I am getting the following failure on my builds today: [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for updates from elca-services [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for updates from codehaus snapshot repository [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for updates from Sakai Plugin Repo [INFO] artifact org.apache.maven.plugins:maven-one-plugin: checking for updates from elca-services [INFO] artifact org.apache.maven.plugins:maven-one-plugin: checking for updates from codehaus snapshot repository [WARNING] repository metadata for: 'artifact org.apache.maven.plugins:maven-one-plugin' could not be retrieved from repository: codehaus snapshot repository due to an error: Error transferring file [INFO] Repository 'codehaus snapshot repository' will be blacklisted Is anyone else seeing this? -AZ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to compile/package files in a module into different jars?
Maven likes 1 artifact per module. So the advice of the guys on IRC is best. What negative side affects are your coders worried about? Wayne On 10/19/07, Quakky [EMAIL PROTECTED] wrote: Hi guys, I have been working with maven for about a week or so, and ive been doing good progress with it, but now im stuck at a point where I dont know how to compile files in a module into different Jars. What I mean by that is lets say I have files A, B and C, and I would like to compile files A and B into 1 Jar, then file C into another jar. How can i achieve this? Someone on IRC channel suggested that I put file C into its own module, but this (according to the coders) has negative side effects. So is there anything that I can do to achieve this? Thanks in advance :-) -- View this message in context: http://www.nabble.com/How-to-compile-package-files-in-a-module-into-different-jars--tf4654180s177.html#a13297497 Sent from the Maven - Users mailing list archive at Nabble.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]
How to compile/package files in a module into different jars?
Hi guys, I have been working with maven for about a week or so, and ive been doing good progress with it, but now im stuck at a point where I dont know how to compile files in a module into different Jars. What I mean by that is lets say I have files A, B and C, and I would like to compile files A and B into 1 Jar, then file C into another jar. How can i achieve this? Someone on IRC channel suggested that I put file C into its own module, but this (according to the coders) has negative side effects. So is there anything that I can do to achieve this? Thanks in advance :-) -- View this message in context: http://www.nabble.com/How-to-compile-package-files-in-a-module-into-different-jars--tf4654180s177.html#a13297497 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: Weird problem with running Junit 3 tests
Problem solved. Apologies for the noise... -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error running Javadoc plugin under CruiseControl
The forward slash may be the problem (a bug). I have no idea. Try
executing mkdir m:/ and see if it works or fails. If it is a
bug, dig into the m-javadoc-p and fix it, and see if that solves your
problem. If so, please file a bug report and attach your fix.
Wayne
On 10/19/07, Simon Kingaby [EMAIL PROTECTED] wrote:
All of the other TARGET folders are created correctly. The error is
strictly relating to the JavaDocs plugin. The checkstyle, PMD,
surefire, docck, etc., all work fine.
Thanks.
Is it important that the folder it is trying to create:
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\com/ski
ngaby/coolcoders/dogHouse/
Has only one \ in the entire path, between apidocs and com?
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 10:29 AM
To: Maven Users List
Subject: Re: Error running Javadoc plugin under CruiseControl
I doubt your CruiseControl user is the same as your regular login user
that you've run your test with. Does the CC user have the proper
privileges to create files/directories on the M: drive etc?
Unable to create directory -- seems like a filesystem problem.
Wayne
On 10/18/07, Simon Kingaby [EMAIL PROTECTED] wrote:
I need some help debugging my Maven 2 script when it runs under
CruiseControl, please.
The javadoc plugin is included in pom.xml with no special parameters:
plugin
artifactIdmaven-javadoc-plugin/artifactId
/plugin
WORKS FROM COMMAND LINE
When I run trunkmvn clean scm:update install site from a Windows
(server 2003 R2) command prompt:
Maven echoes:
[INFO] [javadoc:javadoc]
Loading source files for package com.skingaby.coolcoders.dogHouse...
Constructing Javadoc information...
Standard Doclet version 1.6.0_02
Building tree for all the packages and classes...
Generating
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\com/ski
ngaby/coolcoders/dogHouse/\Cat.html...
Generating
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\com/ski
ngaby/coolcoders/dogHouse/\Dog.html...
...
Generating
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\stylesh
eet.css...
[INFO]
[INFO] BUILD SUCCESSFUL
FAILS IN CRUISECONTROL
I have added the maven plugin to my CruiseControl config.xml:
plugin name=maven2 mvnscript=${env.M2_HOME}/bin/mvn.bat
pomfile=${projectdir}/pom.xml goal=clean scm:update|install
site/plugin
And execute it here:
schedule
maven2/maven2
/schedule
The clean, scm:udpdate and install all work fine. The site however,
fails and the cruisecontrol log shows this:
[INFO] Generate JavaDocs report.
Loading source files for package com.skingaby.coolcoders.dogHouse...
Constructing Javadoc information...
Standard Doclet version 1.6.0_02
Building tree for all the packages and classes...
1 error
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error rendering Maven report: Exit code: 1 - javadoc:
error - Unable to create directory
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\com/ski
ngaby/coolcoders/dogHouse/
com.sun.tools.doclets.internal.toolkit.util.DocletAbortException
at
com.sun.tools.doclets.internal.toolkit.util.DirectoryManager.createDirec
tory(DirectoryManager.java:263)
at
com.sun.tools.doclets.internal.toolkit.util.Util.genWriter(Util.java:576
)
Thank you for your help,
Simon Kingaby
-
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]
Weird problem with running Junit 3 tests
Hello,
I have an annoying problem with running test cases. I have the
following test class:
public class JsTest extends StandaloneTest {
public void testXXX() {
...
}
}
StandaloneTest extends junit.framework.TestCase.
I got the following results:
---
T E S T S
---
Running oqube.js.rpn.JsTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.03
sec
When I make JsTest a direct child of TestCase, it works fine. I have
skimmed through the Jira issues and nothing seems related. I have also
skimmed throught surefire source code and JUnitTestSet seems to
correctly collect subclasses of TestCase. What's wrong with that ?
Thanks in advance,
--
OQube software engineering \ génie logiciel
Arnaud Bailly, Dr.
\web http://www.oqube.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Error running Javadoc plugin under CruiseControl
All of the other TARGET folders are created correctly. The error is
strictly relating to the JavaDocs plugin. The checkstyle, PMD,
surefire, docck, etc., all work fine.
Thanks.
Is it important that the folder it is trying to create:
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\com/ski
ngaby/coolcoders/dogHouse/
Has only one \ in the entire path, between apidocs and com?
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 10:29 AM
To: Maven Users List
Subject: Re: Error running Javadoc plugin under CruiseControl
I doubt your CruiseControl user is the same as your regular login user
that you've run your test with. Does the CC user have the proper
privileges to create files/directories on the M: drive etc?
Unable to create directory -- seems like a filesystem problem.
Wayne
On 10/18/07, Simon Kingaby [EMAIL PROTECTED] wrote:
I need some help debugging my Maven 2 script when it runs under
CruiseControl, please.
The javadoc plugin is included in pom.xml with no special parameters:
plugin
artifactIdmaven-javadoc-plugin/artifactId
/plugin
WORKS FROM COMMAND LINE
When I run trunkmvn clean scm:update install site from a Windows
(server 2003 R2) command prompt:
Maven echoes:
[INFO] [javadoc:javadoc]
Loading source files for package com.skingaby.coolcoders.dogHouse...
Constructing Javadoc information...
Standard Doclet version 1.6.0_02
Building tree for all the packages and classes...
Generating
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\com/ski
ngaby/coolcoders/dogHouse/\Cat.html...
Generating
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\com/ski
ngaby/coolcoders/dogHouse/\Dog.html...
...
Generating
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\stylesh
eet.css...
[INFO]
[INFO] BUILD SUCCESSFUL
FAILS IN CRUISECONTROL
I have added the maven plugin to my CruiseControl config.xml:
plugin name=maven2 mvnscript=${env.M2_HOME}/bin/mvn.bat
pomfile=${projectdir}/pom.xml goal=clean scm:update|install
site/plugin
And execute it here:
schedule
maven2/maven2
/schedule
The clean, scm:udpdate and install all work fine. The site however,
fails and the cruisecontrol log shows this:
[INFO] Generate JavaDocs report.
Loading source files for package com.skingaby.coolcoders.dogHouse...
Constructing Javadoc information...
Standard Doclet version 1.6.0_02
Building tree for all the packages and classes...
1 error
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error rendering Maven report: Exit code: 1 - javadoc:
error - Unable to create directory
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\com/ski
ngaby/coolcoders/dogHouse/
com.sun.tools.doclets.internal.toolkit.util.DocletAbortException
at
com.sun.tools.doclets.internal.toolkit.util.DirectoryManager.createDirec
tory(DirectoryManager.java:263)
at
com.sun.tools.doclets.internal.toolkit.util.Util.genWriter(Util.java:576
)
Thank you for your help,
Simon Kingaby
-
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: Error running Javadoc plugin under CruiseControl
I doubt your CruiseControl user is the same as your regular login user
that you've run your test with. Does the CC user have the proper
privileges to create files/directories on the M: drive etc?
Unable to create directory -- seems like a filesystem problem.
Wayne
On 10/18/07, Simon Kingaby [EMAIL PROTECTED] wrote:
I need some help debugging my Maven 2 script when it runs under
CruiseControl, please.
The javadoc plugin is included in pom.xml with no special parameters:
plugin
artifactIdmaven-javadoc-plugin/artifactId
/plugin
WORKS FROM COMMAND LINE
When I run trunkmvn clean scm:update install site from a Windows
(server 2003 R2) command prompt:
Maven echoes:
[INFO] [javadoc:javadoc]
Loading source files for package com.skingaby.coolcoders.dogHouse...
Constructing Javadoc information...
Standard Doclet version 1.6.0_02
Building tree for all the packages and classes...
Generating
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\com/ski
ngaby/coolcoders/dogHouse/\Cat.html...
Generating
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\com/ski
ngaby/coolcoders/dogHouse/\Dog.html...
...
Generating
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\stylesh
eet.css...
[INFO]
[INFO] BUILD SUCCESSFUL
FAILS IN CRUISECONTROL
I have added the maven plugin to my CruiseControl config.xml:
plugin name=maven2 mvnscript=${env.M2_HOME}/bin/mvn.bat
pomfile=${projectdir}/pom.xml goal=clean scm:update|install
site/plugin
And execute it here:
schedule
maven2/maven2
/schedule
The clean, scm:udpdate and install all work fine. The site however,
fails and the cruisecontrol log shows this:
[INFO] Generate JavaDocs report.
Loading source files for package com.skingaby.coolcoders.dogHouse...
Constructing Javadoc information...
Standard Doclet version 1.6.0_02
Building tree for all the packages and classes...
1 error
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error rendering Maven report: Exit code: 1 - javadoc:
error - Unable to create directory
M:/JavaEnv/Builds/checkout/DogOnAPorch/trunk/target/site/apidocs\com/ski
ngaby/coolcoders/dogHouse/
com.sun.tools.doclets.internal.toolkit.util.DocletAbortException
at
com.sun.tools.doclets.internal.toolkit.util.DirectoryManager.createDirec
tory(DirectoryManager.java:263)
at
com.sun.tools.doclets.internal.toolkit.util.Util.genWriter(Util.java:576
)
Thank you for your help,
Simon Kingaby
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting up company repository
On Fri, October 19, 2007 3:37 pm, Mark Russell wrote: I am trying to setup a maven repository for my company to make artifacts that my company produces available to our developer community. I think I have it setup properly. However, when I run the test pom It can not find the artifacts I have on my company repository. Even with --debug I do not see maven trying to access my repository. Maven will connect to any repos specified in your repositories tags in your POM (or root pom). Run mvn help:effective-pom, and check if the repositories tag exists, and your internal repo is listed correctly. The feature definitely does work, we use it here. Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Javadoc Plugin 2.3 - Generating Doc caused Out of Memory -Xmx doent help
Thanks for your Answer,
i will try that.
- Jens
Also, you're not running out of heap space but of permgenspace.
Try (for maven / antrun plugin) -XX:MaxPermSize=256 or (for the javadoc plugin)
additionalJOption-J -XX:MaxPermSize=256/additionalJOption
Hth,
Nick Stolwijk
-Original Message-
From: Tim Kettler [mailto:[EMAIL PROTECTED]
Sent: Thu 10/18/2007 3:24 PM
To: Maven Users List
Subject: Re: Javadoc Plugin 2.3 - Generating Doc caused Out of Memory -Xmx
doent help
Hi,
in the subject you say genereating the javadoc causes the OOME, but
judging from the log output it seems it's in the antrun-plugin
execution. Have you just tried invoking maven itself with more memory:
mvn -Xmx... or MAVEN_OPTS=-Xmx...
-Tim
Mac-Systems schrieb:
Hello,
since yesterday we never generated Javadoc for our large Multiprojekt.
I included the javadoc plugin and run : mvn site
all is fine so far, javadoc is generated, but in a subprojekt which uses
the generate sources
phase to call some ANT script . Now i get exactly there a out of memory
Error.
Well, i do not believe the error comes from that ANT Plugin (i tested i
already), as Javadoc is the only thing
i changed to my pom for a while, below i tried to set the memory options
for the javadoc plugin whithout
any luck (i get again an OOM Error).
Someone can tell me what i am doing wrong there ?
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.3/version
/plugin
..
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
configuration
links
linkhttp://java.sun.com/j2se/1.5.0/docs/api//link
/links
usefalse/use
quiettrue/quiet
maxmemory1024m/maxmemory
minmemory512m/minmemory
Following output i get:
[INFO] [antrun:run {execution: }]
[INFO] Executing tasks
[echo] Generiere Sourcecode fuer Projekt...
init:
ejbdoclet:
PermGen space
ParameterImpl instances: 0
MethodImpl instances: 0
ConstructorImpl instances: 0
SimpleNode instances: 0
SourceClass instances: 0
XDoc instances:0
DefaultXTag instances: 0
BinaryClass instances: 0
UnknownClass instances:0
Total memory:171
Free memory:90
Try to increase heap size. Can be done by defining ANT_OPTS=-Xmx640m
See the JDK tooldocs.
Before i was using version 2.2 of javadoc Plugin, the output was more
like the standard java out of memory error.
I set also ANT_OPTS to an high value, also which now results.
Anyone can help ?
best regards,
Jens
-
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]
Setting up company repository
I am trying to setup a maven repository for my company to make artifacts that my company produces available to our developer community. I think I have it setup properly. However, when I run the test pom It can not find the artifacts I have on my company repository. Even with --debug I do not see maven trying to access my repository. How do I go about debugging this? Are there any documents on this? -- Mark Russell Instantiations, Inc. 724-368-3331 (land line) http://www.instantiations.com smime.p7s Description: S/MIME Cryptographic Signature
Re: Javadoc Plugin 2.3 - Generating Doc caused Out of Memory -Xmx doent help
Yes,
i've set maven opts up to 1024m.
- jens
Hi,
in the subject you say genereating the javadoc causes the OOME, but
judging from the log output it seems it's in the antrun-plugin
execution. Have you just tried invoking maven itself with more memory:
mvn -Xmx... or MAVEN_OPTS=-Xmx...
-Tim
Mac-Systems schrieb:
Hello,
since yesterday we never generated Javadoc for our large Multiprojekt.
I included the javadoc plugin and run : mvn site
all is fine so far, javadoc is generated, but in a subprojekt which uses
the generate sources
phase to call some ANT script . Now i get exactly there a out of memory
Error.
Well, i do not believe the error comes from that ANT Plugin (i tested i
already), as Javadoc is the only thing
i changed to my pom for a while, below i tried to set the memory options
for the javadoc plugin whithout
any luck (i get again an OOM Error).
Someone can tell me what i am doing wrong there ?
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.3/version
/plugin
..
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
configuration
links
linkhttp://java.sun.com/j2se/1.5.0/docs/api//link
/links
usefalse/use
quiettrue/quiet
maxmemory1024m/maxmemory
minmemory512m/minmemory
Following output i get:
[INFO] [antrun:run {execution: }]
[INFO] Executing tasks
[echo] Generiere Sourcecode fuer Projekt...
init:
ejbdoclet:
PermGen space
ParameterImpl instances: 0
MethodImpl instances: 0
ConstructorImpl instances: 0
SimpleNode instances: 0
SourceClass instances: 0
XDoc instances:0
DefaultXTag instances: 0
BinaryClass instances: 0
UnknownClass instances:0
Total memory:171
Free memory:90
Try to increase heap size. Can be done by defining ANT_OPTS=-Xmx640m
See the JDK tooldocs.
Before i was using version 2.2 of javadoc Plugin, the output was more
like the standard java out of memory error.
I set also ANT_OPTS to an high value, also which now results.
Anyone can help ?
best regards,
Jens
-
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: svn: PROPFIND of Server certificate verification failed: issuer is not trusted
Look in your ${user.home}/.subversion/auth/svn.ssl.server/ directory if your
certificate is correctly stored.
Emmanuel
VanIngen, Erik (ESTG) a écrit :
All,
We are using apache-continuum-1.1-beta-3 on W2000 and are still facing this
error:
svn: PROPFIND request failed on
'/svnroot/giews/gw_giews/trunk/fenix-4domain'
svn: PROPFIND of '/svnroot/giews/gw_giews/trunk/fenix-4domain':
Server certificate verification failed: issuer is not trusted
I already did this trick:
svn list
https://giews.svn.sourceforge.net/svnroot/giews/gw_giews/trunk
and accepted the certificate permanently which is the same as the continuum
user.
What could I do more?
Kind Regards,
Erik
Re: Jabber Recipient Address - Address is invalid
Filed validators for jabber screen are in apps\continuum\webapp\WEB-INF\classes\org\apache\maven\continuum\web\action\notifier\Jabber*NotifierEditAction-jabberProjectNotifierSave-validation.xml files. Emmanuel Vanja Petreski a écrit : Hi, typical JID on my network is [EMAIL PROTECTED] and not [EMAIL PROTECTED] web application has validation, so i can't enter [EMAIL PROTECTED] How to fix that? Thanx, Vanja
Re: M2 release:prepare fails with Subversion to tag SCM reason: Source url is from different repository
Hi, Thanks for your reply! but file:///my/path or file://localhost/my/path or file://127.0.0.1/ my/path, shouldn't all of these work? I don't think this was the cause of my problemmaven was able to commit the modified pom.xml to the trunk however it was unable to create a tag, the process failed at the last step Cheers Ben Tim Kettler wrote: Hi, bmat schrieb: mvn release:prepare --- I recently had this problem using a local installation of subversion and using file uris e.g. developerConnectionscm:svn:file://localhost/repostory/myproject/trunk/developerConnection The syntax for urls is: [protokoll]://[path]. A file url to the path '/my/path' looks like this: file:///my/path You url is missing the leading slash of the path. -Tim I could not get this to work... so I installed Apache 2.0 (Note 2.0 NOT 2.2 cos this doesn't work with subversion apparently). Now using the following (NOTE: the trailing slash! this is important) developerConnectionscm:svn:http://localhost/svn/repository/myproject/trunk//developerConnection this works fine for me (even on windows vista! amazing!) This link was useful : http://www.codeproject.com/w2k/SubversionApache.asp; but the authentication file is wrong i think..at least it didn't work for me. If you change the recommended line from this [/] * = r [test1:/] user1 = rw user2 = [test2:/] user1 = r user2 = rw to this [test1:/myproject] user1 = rw user2 = rw it should work... it is important to specify the repository name here if SVNParentPath is specified in apache httpd.conf. I hope this saves somebody some time and hair as I've nearly pulled all mine out :-) Cheers Ben Markku Saarela wrote: Hi, We are using Maven2 2.0.4 with Subversion 1.3 and now we can't make anymore releases. Previously we success. Here is snippet from parent pom.xml scm connectionscm:svn:svn://fitst37/income/trunk/connection developerConnectionscm:svn:svn://fitst37/income/trunk/developerConnection /scm plugin artifactIdmaven-release-plugin/artifactId configuration usernamesaarfmar/username password12345/password /configuration /plugin Here is output: [INFO] [release:prepare] [INFO] Resuming release from phase 'scm-tag' [INFO] Tagging release with the label 1.0.0... [INFO] Executing: svn --non-interactive copy --file C:\DOCUME~1\saarfmar\LOCALS~1\Temp\maven-scm-108 0661760.commit . svn://fitst37/income/tags/1.0.0 [INFO] Working directory: C:\temp\income [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Source url 'svn://[EMAIL PROTECTED]/income/trunk' is from different repository [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Source url 'svn://[EMAIL PROTECTED]/income/trunk' is from different repository at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor .java:555) Anyone have any idea what do to? Regards, Markku Saarela - 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] -- View this message in context: http://www.nabble.com/M2-release%3Aprepare-fails-with-Subversion--to-tag-SCM-reason%3A-Source-url-is-from-different-repository-tf2213675s177.html#a13294025 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: When builds are done in multi-module projects ?
I have a different problem (continuum 1.0.3): Changes in a project trigger its rebuild, but then another project that depends on the first one is NOT rebuilt. Why is that? Alex Emmanuel Venisse wrote: Continuum look at scm changes, if it contains some sources updates, it build the project. Then, it looks at dependencies list, if a dependency (that is a continuum project too) is updated (new build result in success), continuum build the project With no SCM changes and no dependencies, if the build definition is marked as always build and the build isn't forced, continuum won't build the project. Emmanuel -- View this message in context: http://www.nabble.com/When-builds-are-done-in-multi-module-projects---tf4508232.html#a13293989 Sent from the Continuum - Users mailing list archive at Nabble.com.
RE: Junit 4 or TestNG 5 suite support
Thanks for the response Patrick.
I'm not having problems using Junit 4 (I'm actually using Surefire
version 2.4-collab-SNAPSHOT because 2.4-SNAPSHOT is still broken).
Just having problems getting any of the suite functionality to work.
Frustrating...
-Original Message-
From: Patrick He [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 18, 2007 11:10 PM
To: Maven Users List
Subject: Re: Junit 4 or TestNG 5 suite support
Hello Joel Wiegman,
You can put below lines in your pom.xml for supporting JUnit 4.
build
plugins
plugin
artifactIdmaven-surefire-plugin/artifactId
version2.3/version
/plugin
/plugins
/build
Joel Wiegman wrote:
Members of the Maven council...
Is Surefire's support for suite functionality limited to Junit 3?
TestNG's @BeforeSuite and @AfterSuite annotations are not supported by
Surefire.
Junit 4's equivalent to these methods are to set up a class as
follows:
@RunWith(value=Suite.class)
@SuiteClasses(value={MyFirstTest.class, AnotherTest.class}) public
class AllTests {
@BeforeClass
public void doStuffBeforeSuiteRuns() {
...
}
@AfterClass
public void doStuffAfterSuiteRuns() {
...
}
@Test
public void testMyStuff() {
...
}
}
I then point Surefire to this class and it says no tests were found
(!!!) (and yes, it found the class). Even the testMyStuff() method
was not found as a test!
Is there some matrix out there that shows what annotations are
supported by Surefire? Does anyone else out there have code running
before/after their suites with Junit 4 or TestNG 5? Is my only option
here Junit 3 (frown)?
Thanks so much!
Joel
-
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: how to specify the default email domain ?
no, it isn't possible yet. File an issue and will look at it in next version or maybe before the beta-4/rc-1 release Emmanuel nicolas de loof a écrit : Hello, I'd like continuum to notify developers who broke the build by email. The new Send a mail to latest committers option should solve this, but many developers in my team did not add a developer element in the project POM. Is there any way to make continuum use a default email format ? We all use our corporate ID as subversion login, so just addind @capgemini.fr to the userId will give the expected eMail. Nico.
Re: M2 release:prepare fails with Subversion to tag SCM reason: Source url is from different repository
Hi, bmat schrieb: mvn release:prepare --- I recently had this problem using a local installation of subversion and using file uris e.g. developerConnectionscm:svn:file://localhost/repostory/myproject/trunk/developerConnection The syntax for urls is: [protokoll]://[path]. A file url to the path '/my/path' looks like this: file:///my/path You url is missing the leading slash of the path. -Tim I could not get this to work... so I installed Apache 2.0 (Note 2.0 NOT 2.2 cos this doesn't work with subversion apparently). Now using the following (NOTE: the trailing slash! this is important) developerConnectionscm:svn:http://localhost/svn/repository/myproject/trunk//developerConnection this works fine for me (even on windows vista! amazing!) This link was useful : http://www.codeproject.com/w2k/SubversionApache.asp; but the authentication file is wrong i think..at least it didn't work for me. If you change the recommended line from this [/] * = r [test1:/] user1 = rw user2 = [test2:/] user1 = r user2 = rw to this [test1:/myproject] user1 = rw user2 = rw it should work... it is important to specify the repository name here if SVNParentPath is specified in apache httpd.conf. I hope this saves somebody some time and hair as I've nearly pulled all mine out :-) Cheers Ben Markku Saarela wrote: Hi, We are using Maven2 2.0.4 with Subversion 1.3 and now we can't make anymore releases. Previously we success. Here is snippet from parent pom.xml scm connectionscm:svn:svn://fitst37/income/trunk/connection developerConnectionscm:svn:svn://fitst37/income/trunk/developerConnection /scm plugin artifactIdmaven-release-plugin/artifactId configuration usernamesaarfmar/username password12345/password /configuration /plugin Here is output: [INFO] [release:prepare] [INFO] Resuming release from phase 'scm-tag' [INFO] Tagging release with the label 1.0.0... [INFO] Executing: svn --non-interactive copy --file C:\DOCUME~1\saarfmar\LOCALS~1\Temp\maven-scm-108 0661760.commit . svn://fitst37/income/tags/1.0.0 [INFO] Working directory: C:\temp\income [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Source url 'svn://[EMAIL PROTECTED]/income/trunk' is from different repository [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Source url 'svn://[EMAIL PROTECTED]/income/trunk' is from different repository at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor .java:555) Anyone have any idea what do to? Regards, Markku Saarela - 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: assembly:single failing
Hi, is the pom where the assembly is build also used as the parent pom for the modules? If yes, you've hit a design flaw in maven. Currently, the parent relationship introduces a dependency from child to parent, hence the parent is build first and the artifact of the child doesn't exist yet. Look at your log output, you should see that the parent project is build first. See this thread [1] for an explanation from a developer. If you need to create the assembly attached to the build lifecycle instead of the proposed solution to just build it manually you need to factor out either the parent-pom features or the assembly building stuff to a separate pom. -Tim [1] http://www.nabble.com/Problem-attaching-assembly-to-multi-module-pom-project-tf4576505s177.html#a13063505n [EMAIL PROTECTED] schrieb: Hi again, (thanks to Stéphane Veyret for my previous question, I moved out the phase and goals tags in an execution tag and it is triggered now -- but does not work as expected) I know the subject has been brought up multiple times, but reading the whole summary thread (http://www.mail-archive.com/users@maven.apache.org/msg53354.html, linking to http://jira.codehaus.org/browse/MASSEMBLY-97), I still can not use assembly:single in my multi-module project. My main pom looks like : ... build plugins plugin artifactIdmaven-assembly-plugin/artifactId version2.2-beta-1/version inheritedfalse/inherited configuration appendAssemblyIdfalse/appendAssemblyId descriptors descriptorsrc/main/assembly/assembly.xml/ descriptor /descriptors /configuration executions execution phasepackage/phase goals goalsingle/goal /goals /execution /executions /plugin From what I've read, the phase must be bound for the single goal. If I use 'mvn package' from the command line, I get : [INFO] Failed to create assembly: Artifact: foo:module:jar:3.0.7-SNAPSHOT (included by module) does not have an artifact with a file. Please ensure the package phase is run before the assembly is generated. If it run 'assembly:assembly' from the command line, I get (for the main project) : [INFO] Error reading assemblies: No assembly descriptors found. any idea about why it seems to work for everybody else except me? :) best regards, --Stéphane This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. - Ce message et toutes les pieces jointes (ci-apres le message) sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 release:prepare fails with Subversion to tag SCM reason: Source url is from different repository
mvn release:prepare --- I recently had this problem using a local installation of subversion and using file uris e.g. developerConnectionscm:svn:file://localhost/repostory/myproject/trunk/developerConnection I could not get this to work... so I installed Apache 2.0 (Note 2.0 NOT 2.2 cos this doesn't work with subversion apparently). Now using the following (NOTE: the trailing slash! this is important) developerConnectionscm:svn:http://localhost/svn/repository/myproject/trunk//developerConnection this works fine for me (even on windows vista! amazing!) This link was useful : http://www.codeproject.com/w2k/SubversionApache.asp; but the authentication file is wrong i think..at least it didn't work for me. If you change the recommended line from this [/] * = r [test1:/] user1 = rw user2 = [test2:/] user1 = r user2 = rw to this [test1:/myproject] user1 = rw user2 = rw it should work... it is important to specify the repository name here if SVNParentPath is specified in apache httpd.conf. I hope this saves somebody some time and hair as I've nearly pulled all mine out :-) Cheers Ben Markku Saarela wrote: Hi, We are using Maven2 2.0.4 with Subversion 1.3 and now we can't make anymore releases. Previously we success. Here is snippet from parent pom.xml scm connectionscm:svn:svn://fitst37/income/trunk/connection developerConnectionscm:svn:svn://fitst37/income/trunk/developerConnection /scm plugin artifactIdmaven-release-plugin/artifactId configuration usernamesaarfmar/username password12345/password /configuration /plugin Here is output: [INFO] [release:prepare] [INFO] Resuming release from phase 'scm-tag' [INFO] Tagging release with the label 1.0.0... [INFO] Executing: svn --non-interactive copy --file C:\DOCUME~1\saarfmar\LOCALS~1\Temp\maven-scm-108 0661760.commit . svn://fitst37/income/tags/1.0.0 [INFO] Working directory: C:\temp\income [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Source url 'svn://[EMAIL PROTECTED]/income/trunk' is from different repository [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Source url 'svn://[EMAIL PROTECTED]/income/trunk' is from different repository at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor .java:555) Anyone have any idea what do to? Regards, Markku Saarela - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/M2-release%3Aprepare-fails-with-Subversion--to-tag-SCM-reason%3A-Source-url-is-from-different-repository-tf2213675s177.html#a13293445 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
assembly:single failing
Hi again, (thanks to Stéphane Veyret for my previous question, I moved out the phase and goals tags in an execution tag and it is triggered now -- but does not work as expected) I know the subject has been brought up multiple times, but reading the whole summary thread (http://www.mail-archive.com/users@maven.apache.org/msg53354.html, linking to http://jira.codehaus.org/browse/MASSEMBLY-97), I still can not use assembly:single in my multi-module project. My main pom looks like : ... build plugins plugin artifactIdmaven-assembly-plugin/artifactId version2.2-beta-1/version inheritedfalse/inherited configuration appendAssemblyIdfalse/appendAssemblyId descriptors descriptorsrc/main/assembly/assembly.xml/ descriptor /descriptors /configuration executions execution phasepackage/phase goals goalsingle/goal /goals /execution /executions /plugin From what I've read, the phase must be bound for the single goal. If I use 'mvn package' from the command line, I get : [INFO] Failed to create assembly: Artifact: foo:module:jar:3.0.7-SNAPSHOT (included by module) does not have an artifact with a file. Please ensure the package phase is run before the assembly is generated. If it run 'assembly:assembly' from the command line, I get (for the main project) : [INFO] Error reading assemblies: No assembly descriptors found. any idea about why it seems to work for everybody else except me? :) best regards, --Stéphane This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. - Ce message et toutes les pieces jointes (ci-apres le message) sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.
Jabber Recipient Address - Address is invalid
Hi, typical JID on my network is [EMAIL PROTECTED] and not [EMAIL PROTECTED] web application has validation, so i can't enter [EMAIL PROTECTED] How to fix that? Thanx, Vanja
Maven Release Plugin and autoVersionSubmodules
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, I am having an issue with the release plugin. I am getting an assertion failure just after the plugin asks for the release version to be built (see below for stack trace). Debugging it, it seems the plugin adds the root project id to the release version map twice - the iterator returned in MapVersionsPhase execute method includes the root project (which has already been mapped at that stage) and the ReleaseDescriptor checks for multiple puts into its map. Anyone has any idea why this would happen? Has anyone else seen this issue? Cheers, Johan - 8--- java.lang.AssertionError at org.apache.maven.shared.release.config.ReleaseDescriptor.mapReleaseVersion(ReleaseDescriptor.java:1127) at org.apache.maven.shared.release.phase.MapVersionsPhase.execute(MapVersionsPhase.java:128) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94) - 8--- - -- you too? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHGJO61Tv8wj7aQ34RAhNxAJ4iOUjyXOs52alBdg0eRRWI+n4MVACeKzxv rzvWK13EAx3W8lPRiXqxMrU= =ICPm -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven good Design
Ok, know i'm refactoring project to have something like : project1-ejb project1-sar project2-jar ... In actual Ant build process, some properties files are not embed in jar and are copied in a conf dir (conf directory is in server'sclasspath). Which is the best pratice ? create a new project with only properties file or create a classifier artifact attached to main jar artifact ? Thanks Graham Leggett wrote: On Tue, October 16, 2007 3:44 pm, Saloucious wrote: Ok refactoring projects has been validated !!! Thanks for your reply So, it will be easy now to follow conventions ;-) Yay! Is it a good solution to split project with a dedicated one for each artifacts produced by ANT ? eg: a project for EJB , another for SAR ... Where it makes sense, yes. Maven can be configured to produce multiple artifacts per project, but generally you need to have a deep understanding of the maven lifecycle and what gets built when and in what order, leading to headaches. It is way simpler just to follow the one-artifact-per-project convention. An example of where it may not be necessary is where maven produces two artifacts from the same code, such as an EJB client side interface alongside the EJB implementation. Here maven cannot help but create two artifacts from one project, because the same source code can be used for both. What you'll find is that some of the projects will be very simple. In our case, our ear projects just contain a pom.xml, and nothing else. Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Maven-good-Design-tf4610394s177.html#a13290674 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: Version Ranges Dependency Conflicts
Hi Christian, On 18/10/2007, Christian Weber [EMAIL PROTECTED] wrote: i'm using Maven + Artifactory to manage my Java Projects. Which worked fine so far. But now i'm running into Problem with the Dependency Resolving. I have different Versions of a LibA, e.g.: LibA-1.4.13.9 LibA-1.4.13.55 Now, in my App AppA, i always want to use the newest Version of LibA. So i set the Range of the Dependency of LibA to [1.4.13.1,1.4.13.100]. As Result i get LibA-1.4.13.9 instead of the newer LibA-1.4.13.55. After searching around and testing, it seems, that the 4. Digit ( 9 and 55 ) are compared as String not as Numbers, so that 9 is greater than 55. Unfortuneatly this destroys the Dependency Solving in this Case. I found out, that the standard Maven Version Number is build as follows: Number.Number.Number-String-Number But i need something like Number.Number.Number.Number-String-Number Is there a Possibility to specify, either per Projects (pom.xml) or per Machine (settings.xml) or somehowelse, how a Version Number should look like is it further possible to plug in an own Comparsion Class, which shall be used to compare 2 Versions and decide, which one is newer? Unfortunately not at the moment, but Kenney produced a proposal for improving this in future: http://docs.codehaus.org/display/MAVEN/Versioning Another Problem, reported to me by Colleagues, is the Following: I have a App AppA again, which needs 2 Libs LibA LibB: AppA |- LibA |- LibB Both Libs now need the same LibC. Szenario 1: AppA |- LibA | - LibC 1.4.0.7 |- LibB | - LibC 1.4.0.15 If i compile this Project it successes by choosing one Version of LibC according to my Colleagues, although it should have failed because no common Version is available, which suffices 1.4.0.7 and at the same time 1.4.0.15. How can i solve this? Maven would pick the first version it encounters if they are of equal depth in the dependency tree. To enforce version 1.4.0.7 only, and fail the build in the above example, use the 'hard version' syntax [1.4.0.7]. For more information, see: http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges My last Question is about the Policy of Choosing a the Version of a Lib. Szenario 2: AppA |- LibA | - LibC [1.4.0.7,1.4.0.15] |- LibB | - LibC [1.4.0.4,1.4.0.13] With the standard Policy, the newest common Version is choosen, as far as i understand. So in Szenario 2, LibC-1.4.0.13 is choosen. Is it also possible to instruct Maven to always choose the oldest common Version, so that in Szenario 2, LibC-1.4.0.7 is choosen? Unfortunately not, this is currently hardcoded to pick the newest common version in VersionRange.matchVersion. I agree this should be configurable but am not aware of a raised issue for this? Do raise one if you can't find one. By the way, there's a related issue MNG-612 that provides alternative conflict resolvers for dependency conflicts, although this doesn't extend to resolving version ranges something similar would be required. This Way it is much more suitable for testing, because i can reproduce a specific Build, no matter how many new Version are released in the Meantime. Let me explain, why i need this Szenario 3: AppA |- LibA | - LibC [1.4.0.9,) |- LibB | - LibC [1.4.0.8,) Let's say, that i've tested my Programm AppA with LibC 1.4.0.8 2 Days ago and the Build was successfull. One Day ago a new Version of LibC was released, Version 1.5.0.0. If i now start the same Build Process, it will most problably fail. If Maven would always have choosen the oldest matching Version, the Build will succeed assuming that i didn't change AppA. This would be the Szenario of Testing a specific Build and deploying it some Days later. Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven-scm-provider-starteam
OK, I have raised a JIRA at http://jira.codehaus.org/browse/SCM-349 -- View this message in context: http://www.nabble.com/maven-scm-provider-starteam-tf4647423s177.html#a13290063 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: Problems in option - Release project
Please, file an issue.
Emmanuel
fherrerav a écrit :
Not sure if this have been reported before. I tried to use the release option
on a project but i get an error. It only happens when there are more than
one project in the group. I select one of the projects, clic release and
then shows error. If there is only one project in the group works fine.
Details:
About Continuum
Version:1.1-beta-3
* Browser Firefox 2.0.0.7
HTTP ERROR: 500
Stream closed
RequestURI=/continuum/releaseProjectGroup.action
Powered by Jetty://
* Stacktrace
1265986 [SocketListener0-1] ERROR
com.opensymphony.webwork.components.Component - tag 'select', field 'list',
name 'buildDefinitionId': The requested list key 'buildDefinitions' could
not be resolved as a collection/array/map/enumeration/iterator type.
Example: people or people.{name}
1265987 [SocketListener0-1] INFO
com.opensymphony.xwork.interceptor.Interceptor:exceptionLogging - Error
ocurred during execution
org.apache.jasper.JasperException: tag 'select', field 'list', name
'buildDefinitionId': The requested list key 'buildDefinitions' could not be
resolved as a collection/array/map/enumeration/iterator type. Example:
people or people.{name}
at
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
at
org.mortbay.jetty.servlet.Dispatcher.dispatch(Dispatcher.java:286)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:171)
at
com.opensymphony.webwork.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:114)
at
com.opensymphony.webwork.dispatcher.WebWorkResultSupport.execute(WebWorkResultSupport.java:143)
at
com.opensymphony.xwork.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:313)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:208)
at
org.codehaus.plexus.xwork.interceptor.PlexusReleaseComponentInterceptor.intercept(PlexusReleaseComponentInterceptor.java:69)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.apache.maven.continuum.web.interceptor.ForceContinuumConfigurationInterceptor.intercept(ForceContinuumConfigurationInterceptor.java:72)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:118)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:178)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.codehaus.plexus.xwork.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:58)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at
RepositoryMetadataExceptions
Hi, I think I'm having some progress with my archiva proxy-setup using mirrorOf=*. I started again from scratch, fetched archiva beta2, unpacked, configured all remote repositories I'd need and set up the managed internal repo to be a proxy of them all. As a test, I'm trying to build archiva-beta3 from svn now via 'mvn clean install', with a wiped local repository. (This would be the real smoke-test as other developers will have a clean install of maven with a mirrorOf=* settings and no files in their local repository). The build error looks like this: -- Project ID: org.apache.maven.plugins:maven-clean-plugin Reason: Error getting POM for 'org.apache.maven.plugins:maven-clean-plugin' from the repository: Failed to resolve artifact, possibly due to a repository list that is not appropriately equipped for this artifact's metadata. org.apache.maven.plugins:maven-clean-plugin:pom:2.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) for project org.apache.maven.plugins:maven-clean-plugin -- and Archiva's console output shows this exceptions: -- 2007-10-19 13:06:02,345 [SocketListener0-3] WARN org.apache.maven.archiva.repository.metadata.MetadataTools - Unable to read metadata: /usr/local/java/apache-archiva-1.0-beta-2/data/repositories/internal/org/apache/maven/plugins/maven-clean-plugin/maven-metadata-codehaus.xml org.apache.maven.archiva.repository.metadata.RepositoryMetadataException: file does not exist: /usr/local/java/apache-archiva-1.0-beta-2/data/repositories/internal/org/apache/maven/plugins/maven-clean-plugin/maven-metadata-codehaus.xml -- Where codehaus is the repository name I've chosen for the configured snapshots.repository.codehaus.org. The file does not exists indeed and I get similar exceptions with full stacktraces for most (but not all) of my configured remote repositories. Any ideas what happens here? Kristof
how to specify the default email domain ?
Hello, I'd like continuum to notify developers who broke the build by email. The new Send a mail to latest committers option should solve this, but many developers in my team did not add a developer element in the project POM. Is there any way to make continuum use a default email format ? We all use our corporate ID as subversion login, so just addind @capgemini.fr to the userId will give the expected eMail. Nico.
compilation-error-regexp-alist
Hi, Would any of you Emacs-minded maven 2 users mind sharing your compilation-error-regex-alist with me so I can see what you're doing? I have a regexp that matches the error message but for some reason next-error matches to the beginning of the line, including [INFO] . Very frustrating! Thanks, Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: When builds are done in multi-module projects ?
Alex Tanaev a écrit : I have a different problem (continuum 1.0.3): Changes in a project trigger its rebuild, but then another project that depends on the first one is NOT rebuilt. dependant projects are rebuilt in Continuum 1.1 not in 1.0.3 Emmanuel Why is that? Alex Emmanuel Venisse wrote: Continuum look at scm changes, if it contains some sources updates, it build the project. Then, it looks at dependencies list, if a dependency (that is a continuum project too) is updated (new build result in success), continuum build the project With no SCM changes and no dependencies, if the build definition is marked as always build and the build isn't forced, continuum won't build the project. Emmanuel
