Re: [maven-surefire-plugin] Issue with -Dtest param under Windows

Cheers Dan!! just works as expected with 2.11. Just wondering why I'm so quick to upgrade to newer versions sometimes... -- View this message in context: http://maven.40175.n5.nabble.com/maven-surefire-plugin-Issue-with-Dtest-param-under-Windows-tp5518723p5521282.html Sent from the Maven -

[maven-help-plugin] bug with active-profiles in 2.1.1

maven-help-plugin:2.1.1:active-profiles doesn't display some active profiles under a specific set of circumstances: - a parent pom containing a set of profiles, let's say 'dev' and 'prod' - a settings.xml that activates a locally defined plugin (let's call it 'repo'), and also activates the

[maven-surefire-plugin] Issue with -Dtest param under Windows

I'm having an issue with 'mvn test -Dtest=testClassName' It works fine under Linux and OsX but under Windows the test is simply not found. I'm using latest TestNG. Any clue on what the problem could be? -- View this message in context:

Re: [maven-site-plugin] trouble migrating from 3.0-beta3 to 3.0, bug?

-Original Message- From: nodje [mailto:[hidden email] /user/SendEmail.jtp?type=nodenode=5509501i=1] Sent: Thursday, February 23, 2012 12:23 AM To: [hidden email] /user/SendEmail.jtp?type=nodenode=5509501i=2 Subject: Re: [maven-site-plugin] trouble migrating from 3.0-beta3 to 3.0, bug? Hum, I

Re: [maven-site-plugin] trouble migrating from 3.0-beta3 to 3.0, bug?

apache email. cheers Olivier Lamy [via Maven] wrote: Hello, Do you have a sample project to reproduce that ? 2012/2/22 nodje [hidden email] /user/SendEmail.jtp?type=nodenode=5505481i=0: migration form 2.x to 3.0-betax wasn't much of a problem, but since then, I had to release components

[maven-site-plugin] trouble migrating from 3.0-beta3 to 3.0, bug?

=pluginorg.apache.maven.plugins:maven-site-plugin:3.0 strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy urls[0] = file:/Users/nodje/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.jar urls[1] = file:/Users/nodje/.m2/repository/org/apache/maven/reporting/maven

Re: [maven-failsafe-plugin] Running integration test with its own profile

Hi Ron, I've been reading quite some of your posts in the forum, and it actually changed my mind about deployment configuration. Enlightening indeed. I would now try to favor a single artifact deployment that could be configured externally - say JNDi, this really makes sense. That said, I

[maven-failsafe-plugin] Running integration test with its own profile

Hi, I'm facing a problem in the release process when running Integration Tests. We have different profiles for the different environments the release is made for, namely DEV, TEST, PROD. Each profile has its own values for DB access. Now the IT are made to work on the development environment,

Re: [maven-failsafe-plugin] Running integration test with its own profile

Invaluable piece of information Ron, thanks a lot. I've been searching the archives without success, with 'profile plugin' 'failsafe profile', all woudn't yield much relevant results. But I'd still be happy if you could point me to some efficient keywords to search for. I don't remember JNDI as

[maven-release-plugin] using scm definition in parent pom for all project

Hi, we've been using a definition of scm located in our company parent pom: scm connectionscm:svn:${svn.root}/trunk/${artifactId}/connection developerConnectionscm:svn:${svn.root}/trunk/${artifactId}/developerConnection url${svn.root}/trunk/${artifactId}/url /scm This used to work

[maven-failsafe-plugin] Failsafe+Jetty integration test trigger surefire twice

I've been using the standard configuration described in http://maven.apache.org/plugins/maven-failsafe-plugin/usage.html to be able to execute integration tests. That is, jetty:run-exploded goal is link to pre-integration-test phase in order to have a container to run integration test against.

Re: [maven-failsafe-plugin] Failsafe+Jetty integration test trigger surefire twice

Hi Stephen, I like your second post ;) One the other hand it probably means that you already know that pestering jetty plugin people won't help! still, it's frustrating to see some phase triggered more than what is needed. I guess i have better things to do than trying to perfect something

Need help to find best way to recompile complete project and dep with 1.5

adding another intermediary parent pom, (something like all-parent-jdk1.5) to see if it would propagate the jar plugin config as expected. cheers /nodje -- View this message in context: http://n2.nabble.com/Need-help-to-find-best-way-to-recompile-complete-project-and-dep-with-1-5-tp4413579p4413579

Re: [Release] scm getting rewritten. how does it work?

appended to the inherited scm url -Stephen 2009/12/3 nodje nodje...@gmail.com: Hi, I'm using maven-release-plugin 2.0-beta9 and I'm still getting scm urls rewritten at each deployment. http://jira.codehaus.org/browse/MRELEASE-231 is been closed quite a while ago, so many we're

[Release] scm getting rewritten. how does it work?

Hi, I'm using maven-release-plugin 2.0-beta9 and I'm still getting scm urls rewritten at each deployment. http://jira.codehaus.org/browse/MRELEASE-231 is been closed quite a while ago, so many we're not speaking about the same rewriting. The way we use the SCM tag in our organization is trough

buildnumber-maven-plugin using svnjava doesn't detect SVN working copy

] [ERROR] BUILD ERROR [INFO] [INFO] Cannot get the revision information from the scm repository : Exception while executing SCM command. svn: '/Users/nodje/Documents/project

Re: buildnumber-maven-plugin using svnjava doesn't detect SVN working copy

://jira.codehaus.org/browse/MAVENUPLOAD-2533 2009/8/25 nodje nodje...@gmail.com: I got an error using 1.0-beta-3 with svnjava: [INFO] [buildnumber:create {execution: default}] [INFO] Change the default 'svn' provider implementation to 'javasvn'. [INFO] Checking for local modifications: skipped. [INFO

Tomcat Maven Plugin doesn't seem to take webapps/META-INF/context.xml into account

I'm trying to make use of context.xml with the Tomcat Maven Plugin. Whether I use tomcat:run or tomcat:deploy, it invariably deploys to a context based on the pom's artifactId an not to the context path specified in the webapps/META-INF/context.xml. Has anyone met the issue? -- View this

Maven Surefire Plugin suiteXmlFiles config in parent pom doesn't seem to work

Hi, I'm trying to get a single test configuration for all projects and as such I'm trying to put this piece of config in a parent pom: suiteXmlFiles suiteXmlFilesrc/test/testng.xml/suiteXmlFile /suiteXmlFiles But it doesn't seem

Re: Using buildnumber-maven-plugin together with jetty plugin

Hi Olivier, I got an error following the update of builnumber-maven-plugin 1.0-beta-3-SNAPSHOT: [INFO] Error building POM (may not be this project's POM). Project ID: org.codehaus.mojo:buildnumber-maven-plugin Reason: Failed to build model from file '/Users/nodje/.m2/repository/org/codehaus

Re: Linking source javadoc plugin to install phase - limitation?

/execution In this case, the source and javadoc artifacts are created, but they won't be installed in the local repo nor will they be deployed. Why is that? -nodje nodje wrote: Hi, I'm trying to limit the creation of Sources and Javadoc jars to goals only after install. Currently

Re: Using buildnumber-maven-plugin together with jetty plugin

/ 2009/4/17 nodje nodje...@gmail.com: Olivier, i'm getting those log lines for each mavengoal invoked: [WARNING] Attempting to build MavenProject instance for Artifact (org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-3-20090414.214556-8) of type: maven-plugin; constructing POM artifact

Re: Using buildnumber-maven-plugin together with jetty plugin

a bit on this please? thanks -nodje 2009/4/14 Olivier Lamy ol...@apache.org: 2009/4/14 nodje nodje...@gmail.com: Hi Olivier, it does actually help! It works in IDEA now. But if it can filter the ${timestamp}, it doesn't work anymore for ${buildNumber}: [INFO] [buildnumber:create

Re: Using buildnumber-maven-plugin together with jetty plugin

It works fine now, thanks a lot! -nodje 2009/4/14 Olivier Lamy ol...@apache.org: 2009/4/14 nodje nodje...@gmail.com: Hi Olivier, it does actually help! It works in IDEA now. But if it can filter the ${timestamp}, it doesn't work anymore for ${buildNumber}: [INFO] [buildnumber:create

Re: Using buildnumber-maven-plugin together with jetty plugin

that are used only for creating WAR to deploy, and that's perfect here. People should be able to learn to do that outside of IDEA. thanks -nodje because executing mojos directly never invokes the lifecycle. you could have a profile with a default goal of validate and with the plugins you want bound

Linking source javadoc plugin to install phase - limitation?

/phase is included in the plugin. -nodje -- View this message in context: http://n2.nabble.com/Linking-source---javadoc-plugin-to-install-phase---limitation--tp2626903p2626903.html Sent from the maven users mailing list archive at Nabble.com

Re: Using buildnumber-maven-plugin together with jetty plugin

Thanks for the info Stephen. I didn't expected a new release of SVN so soon! SVNKIT's probably gonna solve the problem. Changing the SVN CLI's not gonna help anyway, and as far as I'm concerned no Macport available for 1.6 yet! I'll be watching that. cheers 2009/4/13 nodje nodje...@gmail.com

Re: Using buildnumber-maven-plugin together with jetty plugin

the latest version of the plugin: [INFO] [buildnumber:create {execution: default}] [INFO] Checking for local modifications: skipped. [INFO] Updating project files from SCM: skipped. [INFO] Executing: /bin/sh -c cd /Users/nodje/Documents/project/company/project svn --non-interactive info [INFO] Working

Re: Using buildnumber-maven-plugin together with jetty plugin

On Thu, Apr 9, 2009 at 7:32 AM, Dan Tran dant...@gmail.com wrote: I may be wrong, but i think finalName is constructed early in the cycle and therefor buildNumber var is not propagate properly, does maven 2.1.0 help? No, the problem is that since Nodje is executing jetty plugin directly rather

Using buildnumber-maven-plugin together with jetty plugin

it seems Jetty isn't aware of the ${buildNumber} variable when it check the name of the war it has to deploy. Did anyone successfully use both plugin together? cheers -nodje -- View this message in context: http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin

Getting timestamp as a Maven property

This seems to have been fixed in 2.1.0 (cf. http://jira.codehaus.org/browse/MNG-2562) but I can't find any information on how this has actually been implemented. How can I have access to this property? thanks! -nodje -- View this message in context: http://n2.nabble.com/Getting-timestamp

Re: Parents version isn't check for new updates on the remote repository

A month later, I'm still confronting the same problem... Is there anything obvious I'm missing here? Am I the only one trying to figure this out? :-/ nodje wrote: Sorry for not being clear. What I mean is that the regular way Maven checks for updates on SNAPSHOT dependencies doesn't

Re: Parents version isn't check for new updates on the remote repository

hum, still no one about this? It'd really help to solve the issue though. nodje nodje wrote: Sorry for not being clear. What I mean is that the regular way Maven checks for updates on SNAPSHOT dependencies doesn't apply to parent-pom SNAPSHOT. If you have a project with a parent-pom 1

Re: Filtering TestResources

Hi, it seemed to work at first, but now we get the main/resources filtered by the test/filters. We have to revert on naming properties differently :( -nodje Olivier Lamy wrote: Hi, As we have an it test [1] which test this and works, it should :-) -- Olivier [1] https

Re: Filtering TestResources

Is http://jira.codehaus.org/browse/MRESOURCES the right place to submit the issue? As for the test case, what about a pom.xml with the minimal directory structure and a couple of properties files and filters. Can I update that on Jira? -nodje Olivier Lamy wrote: Can you load an issue

Re: Parents version isn't check for new updates on the remote repository

doesn't seem to appear in the mailing list. Explanation welcome!! -nodje Wayne Fay wrote: In other words, it seems there is no update checks on the remote repo for the parent version in a child project. Is that an expected behavior? If not, is there a bug filled alreay for that? Is there any

Parents version isn't check for new updates on the remote repository

the latest version. In other words, it seems there is no update checks on the remote repo for the parent version in a child project. Is that an expected behavior? If not, is there a bug filled alreay for that? Is there any workaround ? cheers nodje -- View this message in context: http

Re: Filtering TestResources

I'm running into the exact same problem. I'd be really convenient to be able to keep the same properties name. Could someone confirm this is a problem or the expected behavior? Is there any workaround? apart from renaming properties? cheers -nodje rundmsef wrote: If you are attempting

Re: Filtering TestResources

it should only specify the default version to use when you include the plugin in your pom and not add the plugin to each every Maven project. But it seems it does. I'm gonna try the 2.3 version then. Is it supposed to work with this one? -nodje olamy wrote: Hi, Which version of the resources

Re: release pluging not workin?

-style) [INFO] [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: svn --non-interactive status [INFO] Working directory: /Users/nodje/Documents/Project/company/company-parent-1 [INFO

release pluging not workin?

... [INFO] Executing: svn --non-interactive status [INFO] Working directory: /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT [INFO] Checking dependencies and plugins for snapshots ... There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes

problem with release:prepare in resolving dependency

... [INFO] Executing: svn --non-interactive status [INFO] Working directory: /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT [INFO] Checking dependencies and plugins for snapshots ... There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes

Re: How to override properties selectively with multiple filter files or profiles

I'm currently having the same problem as below. Not migrating from ant though, but I need to be able to filter different set of properties having the same name. I don't think it's possible to affect a specific filter to a chosen resource. To illustrate, let's say you have two instances of an

Re: Archetype:create broken?

mvn archetype:generate produce the same error. Could it have something to do with the velocity-1.5.pom that it doesn't find? nodje wrote: Sorry didn't pay attention to that. But the result is exactly the same with generate anyway. Looks like you don't have the problem, so it's probably

Re: Archetype:create broken?

of create ? create goal is deprecated as far as I know. Marc. nodje a écrit : What's with the archetype:create? I suddenly get this error when trying to create a new project: mvn archetype:create -DgroupId=com.company.commons -DartifactId=xml [INFO] Scanning for projects... [INFO

Archetype:create broken?

dependency on commons-lang -nodje -- View this message in context: http://www.nabble.com/Archetype%3Acreate-broken--tp17503659p17503659.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail

dependency:sources, dependency:javadoc???

, -nodje -- View this message in context: http://www.nabble.com/dependency%3Asources%2C-dependency%3Ajavadoctp16392437s177p16392437.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail

Re: dependency:sources, dependency:javadoc???

, nodje [EMAIL PROTECTED] wrote: Is there a way to get a project dependencies' javadoc jars? I expected something quite simple in the line of the dependency-plugin goal 'dependency:sources' but it lokks like there's nothing to get the javadocs along the sources. What would be the best

force dependency sources javadocs to be retrieved

I'd like to make sure all developers have a project dependencies' javadocs sources at disposal in their private repository. Can I modify the dependency:resolve default behavior to achieve this? NB: it mustn't be linked to a Maven lifecycle goal. --nodje -- View this message in context: http

RE: force dependency sources javadocs to be retrieved

I assumed Maven was resolving dependencies using the plugin goal 'resolve'. If so, what would be a better place to tell Maven to fetch sources along with the libraries? Otherwise can a call to dependency:sources be added somewhere in the lifecycle? -nodje Brian E Fox wrote

RE: Release cycle - Maven release plugin usability

-tags instead of just /tags. Every build goes to build-tags automatically. When a release occurs, we move the tag to release tags and delete the other build tags. -Original Message- From: nodje [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 26, 2008 11:05 PM To: users

Release cycle - Maven release plugin usability

instead of tag? thanks for any feedback, I'm a little bit lost here :) --nodje -- View this message in context: http://www.nabble.com/Release-cycle---Maven-release-plugin-usability-tp16296781s177p16296781.html Sent from the Maven - Users mailing list archive at Nabble.com

Re: Release cycle - Maven release plugin usability

. there was a big fubar with 1.2.3-TEST-1, so we're going again then you have 1.2.3-TEST-2) When you are finally ready to roll you just go 1.2.3-TEST-x - 1.2.3 On Wed, Mar 26, 2008 at 7:36 AM, nodje [EMAIL PROTECTED] wrote: I'm not 100% sure it's the right forum to ask question about

Is there really a problem with the plugin repository???

on a fresh Windows installation. Fresh installation downloaded many artifacts, but ended up with the same error. I'm lost here. Is there anything else I can try. Something obvious I haven't check? Or is there really a problem with the main repo? --nodje -- View this message in context: http

RE: Is there really a problem with the plugin repository???

help Brian. Brian E Fox wrote: We need more info to help. What plugin artifact is missing? Paste the relevant part of your log output. -Original Message- From: nodje [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2008 2:47 AM To: users@maven.apache.org Subject

Release plugin overwrite scm config

by the release plugin's prepare goal. I don't think it's necessary to overwrite this config information. Why is that so? Is there anyway to avoid this? I don't see any option allowing to do this. --nodje -- View this message in context: http://www.nabble.com/Release-plugin-overwrite-%3Cscm%3E-config

Maven plugin version and information

plugin: what's the difference between 2.0 and 2.0.2? and what's new in 2.1-alpha? cheers --nodje -- View this message in context: http://www.nabble.com/Maven-plugin-version-and-information-tp15750775s177p15750775.html Sent from the Maven - Users mailing list archive at Nabble.com

Maven Resources Plugin Windows path \\ parsing problem

haven't found anything on the subject. Has anyone encountered the same issue? cheers, --nodje -- View this message in context: http://www.nabble.com/Maven-Resources-Plugin-Windows-path-%5C%5C-parsing-problem-tp15449734s177p15449734.html Sent from the Maven - Users mailing list archive

Remote repository problems

[1] as does the other one [2] Hth, Nick Stolwijk [1] http://repo1.maven.org/maven2/classworlds/classworlds/1.1-alpha-2/ [2] http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-container-default/1.0-alpha-8/ nodje nodje wrote: i'm probably the nth guy to ask this, but I'm

mvn test : surefire dependency problem

i'm probably the nth guy to ask this, but I'm totally new to maven and barely understand it: i cannot 'mvn test', I get: [INFO] Error to resolving surefire provider dependency: Missing: -- 1) classworlds:classworlds:jar:1.1-alpha-2 Try downloading the file manually from the project