[Announce] Release of SonarQube Maven Plugin 2.5
Hi, The Mojo team is pleased to announce the release of the SonarQube Maven Plugin version 2.5. This plugin aims at running SonarQube analysis for Maven projects. http://mojo.codehaus.org/sonar-maven-plugin/index.html To get this update, simply specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdsonar-maven-plugin/artifactId version2.5/version /plugin Release Notes ** Bug * [MSONAR-87] - Maven encryption conflict with SonarQube encryption ** Improvement * [MSONAR-91] - sonar.skip in multi modules project * [MSONAR-104] - Avoid nested source folders ** Task * [MSONAR-93] - Provide project dependencies for SonarQube 5.0 * [MSONAR-103] - Use new Java specific properties to specify classpath Enjoy, The Mojo team. Julien HENRY - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[Announce] Release of SonarQube Maven Plugin 2.4
Hi, The Mojo team is pleased to announce the release of the SonarQube Maven Plugin version 2.4. This plugin aims at running SonarQube analysis for Maven projects. http://mojo.codehaus.org/sonar-maven-plugin/index.html To get this update, simply specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdsonar-maven-plugin/artifactId version2.4/version /plugin Release Notes * [MSONAR-70] - Use every available sonar.* property when running an analysis with Maven * [MSONAR-75] - Remove unexisting entries from sonar.sources and sonar.tests on projects with packaging=pom * [MSONAR-81] - On war modules the directory containing the web resources (src/main/webapp by default) should be automatically added to sonar.sources * [MSONAR-82] - By default the pom.xml file should be part of sonar.sources * [MSONAR-83] - Populate sonar.libraries Enjoy, The Mojo team. Julien HENRY - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] SonarQube Maven Plugin 2.3.1 Released
Hi, The Mojo team is pleased to announce a bugfix release of the SonarQube Maven Plugin version 2.3.1. This plugin aims at running SonarQube analysis for Maven projects. http://mojo.codehaus.org/sonar-maven-plugin/index.html To get this update, simply specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdsonar-maven-plugin/artifactId version2.3.1/version /plugin Release Notes * [MSONAR-77] - Unable to analyze deep multi-module projects on SonarQube 4.3+ Enjoy, The Mojo team. Julien HENRY - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] SonarQube Maven Plugin 2.3 Released
Hi, The Mojo team is pleased to announce the release of the SonarQube Maven Plugin version 2.3. This plugin aims at running SonarQube analysis for Maven projects. http://mojo.codehaus.org/sonar-maven-plugin/index.html To get this update, simply specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdsonar-maven-plugin/artifactId version2.3/version /plugin Release Notes * [MSONAR-46] - Add the skip option * [MSONAR-61] - Improve support of advanced reactor options * [MSONAR-69] - Support Maven encryption mechanism for SonarQube passwords * [MSONAR-60] - Embed sonar-runner Enjoy, The Mojo team. Julien HENRY - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Deploying to dav repo behind a proxy
Hi,
Does someone have a working configuration for deploying artifacts to a dav
repository from behind a proxy with Maven 2.2.1 AND Maven 3.0.x?
Currently I only managed to have something working with Maven 3.0.x but I still
have the polluting message:
SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
(not a bloquer but annoying for users)
No solution seems to work with Maven 2.2.1.
-- FIRST TRY --
My company uses an http proxy so in my settings.xml I have something like:
proxy
idmyproxy/id
activetrue/active
protocolhttp/protocol
usernameuser/username
passwordpwd/password
hostproxy.mycompany.fr/host
port3128/port
nonProxyHostslocalhost,*.mycompany.fr/nonProxyHosts
/proxy
In my parent pom the version of the maven-deploy-plugin is set to 2.7.
Fail with Maven 2.2.1:
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from codehaus.org
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] Connecting to repository: 'codehaus.org' with url:
'dav:https://dav.codehaus.org/snapshots.repository/sonar-plugins';.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error retrieving previous build number for artifact
'org.codehaus.sonar-plugins:sonar-violationdensity-plugin:sonar-plugin':
repository metadata for: 'snapshot
org.codehaus.sonar-plugins:sonar-violationdensity-plugin:1.3-SNAPSHOT' could
not be retrieved from repository: codehaus.org due to an error: dav.codehaus.org
[...]
Caused by: java.net.UnknownHostException: dav.codehaus.org
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:175)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384)
at java.net.Socket.connect(Socket.java:546)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:584)
at sun.security.ssl.SSLSocketImpl.init(SSLSocketImpl.java:426)
at
sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:142)
at
hidden.org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:81)
at
hidden.org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:126)
at
hidden.org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)
at
hidden.org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1321)
at
hidden.org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)
at
hidden.org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at
hidden.org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at
hidden.org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
at
org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.execute(AbstractHttpClientWagon.java:446)
at
org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:561)
Fail with Maven 3.0.4:
Caused by: org.sonatype.aether.transfer.NoRepositoryConnectorException: No
connector available to access repository codehaus.org
(dav:https://dav.codehaus.org/snapshots.repository/sonar-plugins) of type
default using the available factories WagonRepositoryConnectorFactory
at
org.sonatype.aether.impl.internal.DefaultRemoteRepositoryManager.getRepositoryConnector(DefaultRemoteRepositoryManager.java:400)
at
org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:231)
... 26 more
-- SECOND TRY --
So I have added the webdav wagon extension in my parent pom:
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-webdav-jackrabbit/artifactId
version2.2/version
/extension
Fail with Maven 2.2.1:
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from codehaus.org
SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder.
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
[...]
Caused by: java.lang.ClassNotFoundException: org.slf4j.impl.StaticLoggerBinder
Success with Maven 3.0.4 but display warning:
SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See
Re: How to generate dependency diagram like on http://maven.apache.org/ref/3.0.3/
Hi, It is manually done with OpenOffice/LibreOffice: http://svn.apache.org/viewvc/maven/maven-3/trunk/src/site/xdoc/maven-deps.odg Regards, Julien - Mail original - De : Ansgar Konermann ansgar.konerm...@googlemail.com À : Maven Users List users@maven.apache.org Cc : Envoyé le : Mardi 27 Décembre 2011 23h10 Objet : How to generate dependency diagram like on http://maven.apache.org/ref/3.0.3/ Hi all, I'd like to create a dependency diagram like the one depicted on http://maven.apache.org/ref/3.0.3/ How did this diagram get generated, or was it done by hand using an off the shelf drawing program? Kind regards Ansgar - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Checksum issue with webdav deploy
Hi,
I was bitten by bug OutOfMemory when deploying big files
(http://jira.codehaus.org/browse/WAGON-272) so I decided to switch to dav
protocol. In my pom I have added dav: in front of URL in
distributionManagement section, and also added webdav wagon this way:
build
pluginManagement
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.7/version
dependencies
dependency
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-webdav-jackrabbit/artifactId
version2.1/version
/dependency
/dependencies
/plugin
...
Then I tried to deploy on our Nexus repo using Maven 2.2.1, and the result was
corrupted md5 checksum for all files (pom, metadata.xml, ...). My feeling was
that it was not the correct wagon that was used (I suppose the one included in
Maven 2.2.1 takes priority over the one declared as dependency of m-deploy-p).
So I tried to switch to an extension:
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-webdav-jackrabbit/artifactId
version2.1/version
/extension
/extensions
But then my build failed with the following error:
[INFO] [deploy:deploy {execution: default-deploy}] [INFO] Retrieving previous
build number from macif-snapshots-repo
SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder.
...
[ERROR] BUILD ERROR
...
Caused by: java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder at
org.slf4j.LoggerFactory.getSingleton(LoggerFactory.java:230) at
org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) at
org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:112) at
org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:275) at
org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:248) at
org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:155)
at
org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:131)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:685) at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.clinit(MultiThreadedHttpConnectionManager.java:70)
at
org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.init(AbstractHttpClientWagon.java:181)
at
org.apache.maven.wagon.providers.webdav.WebDavWagon.init(WebDavWagon.java:64)...
Any suggestion?
My need is to be able to deploy big files with Maven 2.2.1 and/or Maven 3.0.3.
I can do any modification in our corporate pom but I don't want to rely on
anything in settings.xml as I can't be sure users will do the modification and
I don't want to corrupt my repository.
Thanks
Julien
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How to run a plugin across all modules during release:perform
Hi, Maybe it is related to @aggregator on the goal of the plugin? http://maven.apache.org/developers/mojo-api-specification.html Regards, Julien - Mail original - De : Ben Tatham bentat...@nanometrics.ca À : users@maven.apache.org Cc : Envoyé le : Mercredi 7 Décembre 2011 15h41 Objet : How to run a plugin across all modules during release:perform Hi, We have a custom plugin that runs whenever we release a project. Most of our projects are _not_ multi-module, so it generally works fine by adding that plugin to the release-plugin goals. However, when I add that into the root pom of a multi-module build, it only runs on the top-level project, even though the modules inherit from that pom and do declare maven-release-plugin so in theory, it should pick up that configuration. Is there a way to force the plugin to run in each module during release? I've explored options on the plugin itself [1] and options on the maven-release-plugin[2] , but can't find anything about this issue. Specifically, our plugin goes through our scm repository and updates the dependencies in all our designated pom's to the newly released version of the project being released - so we also want the module projects to get updated in our repository. Thanks, Ben [1] http://maven.apache.org/developers/mojo-api-specification.html [2] http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html -- Ben Tatham Software Developer Nanometrics Inc. +1 613-592-6776 x254 http://www.nanometrics.ca - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Invalid pom in a range = unable to build
Hi, I have a project using a range as version for a dependency. From Maven 3 release notes I can see that: Last but not least, Maven 3 inspects the POMs of all matching versions when processing version ranges to enable sophisticated conflict resolution. My concern is that among all versions of the dependency matching the range, there is one with a broken POM. Because there is a newer version that is not broken, I was expecting the build to complete. But it seems it is not the case. I have an error like this: Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project X: Failed to collect dependencies for [..] ... Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for (where is not the newest version in the range). A solution could be to fix or remove the broken version from my corporate repository, but AFAIK this is not a scalable solution (it would require to clean all private repos in the company). When not using range, the Maven way is to release a new fixed version of an artifact when something goes wrong. But with range it doesn't work. Would it be possible to ignore broken candidates when processing a range? At least when this is not the last version. Thanks Julien - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Reactor doesn't build parent poms first?
Same use case for me. Most of the time users work on single module. But we also create artificially (using svn:externals) big multimodule builds with an aggregator pom. This is to allow a full clean build on CI platform. relativePath is set to empty in order to avoid maven complains when working on a single component. So in our big build we have A, B and C in this order where B is parent of A and C. Doing mvn clean install, A will get old parent from repo (when available) while C will get newest parent that was installed just before. I feel reordering reactor by taking parent relationship into account can solve this issue. Regards Julien - Mail original - De : Laird Nelson ljnel...@gmail.com À : Maven Users List users@maven.apache.org Cc : Envoyé le : Lundi 22 Août 2011 17h38 Objet : Re: Reactor doesn't build parent poms first? On Mon, Aug 22, 2011 at 11:22 AM, Benson Margulies bimargul...@gmail.comwrote: I'm foggy on one point here. How can the pom in the reactor differ from the pom reached by relative path? Different property substitutions? Or is the issue here the case in which there is no rel path, but it is in the reactor? (I'll quickly chime in with my background use case--or at least the reason why I brought up all this stuff initially.) In my organization we have lots of modules. Developers typically only work on a given module at a time. We've set things up in a pretty standard fashion so that they can check that module out and work on it without having to check out the other modules. We've got Nexus proxying various repositories; all artifacts that are depended upon basically get downloaded through that. Standard Maven stuff. Of course, the developers often do have the whole project checked out. That used to cause some weird problems, detailed below. Some of our modules have parents that are other modules. So we have a standard -pomtypes-jpa module, for example, that does some stuff in its build section to do things like generate the list of entity classes that should be included in a persistence.xml during unit/integration testing. Other modules may extend this as their parent to pick up this behavior. Occasionally, we need to make changes to these mid-level modules. Back in the day, we had a bunch of relativePath elements. But developers were getting confused, because if they were working on a JPA module that inherited from this -pomtypes-jpa module, then if they hadn't version-control-updated their -pomtypes-jpa module, the relativePath element would kick in and try to use the working copy in their workspace. Oops. The solution in this case was: if you have the -pomtypes-jpa module checked out, make sure you svn update it religiously so that when relativePath finds it, you're getting the most recent copy from Subversion. OK, fine, so we finally decided, forget this, the relativePath element is kind of a hack anyway (or at least didn't fit our needs at all). So now all pom resolution comes from the repository. That's cool; that's like every other Maven artifact. Smooth sailing. We update the -pomtypes-jpa pom.xml, and all children who extend it pick it up automatically (we're still in SNAPSHOT mode). However, this is kind of odd when we're doing a full build. Suppose one of these developers hasn't done a full build in ages and ages. Or, for that matter, hasn't worked on a JPA module, so hasn't caused Maven to go look for a new SNAPSHOT version of that -pomtypes-jpa project. Now, when we execute that full build right after a global svn update, the full build will go use the (comparatively ancient) 1.0-SNAPSHOT version of -pomtypes-jpa's pom.xml from the local repository (or the remote), which is, of course, the most recent *deployed* version, but might very well not be the most recent version *in Subversion* that they just checked out to their workspace. Really since we're doing a full build, we'd like it to use...well, the one that should be built right now. :-) We would like it to realize that one of the artifacts that a module extends from is actually *in the build plan currently being executed*, so gee, it would be nice if Maven would sort it all the way up in the topologically sorted list of reactor projects. Obviously it could potentially affect property substitution and the like for child poms, so you'd want to make sure this thing was built first. Maybe that's all backwards and wrong-headed, but it's where I was coming from. One customer's input. The workaround for us is to wrap Maven so that we do mvn -o clean install on the parent poms first, in topological order, then run mvn clean install from the root. I was looking for this sort of thing to be handled natively by the reactor. Best, Laird -- http://about.me/lairdnelson - To unsubscribe, e-mail:
Re: Reactor doesn't build parent poms first?
According to my own tests, with Maven 3 the parent pom is resolved according to the following algorithm: IF relativePath != THEN IF pom is found at relativePath location and GAV match THEN use this pom as parent ELSE log a warning and useRepo=true ENDIF ELSE useRepo=true ENDIF Maven 3 will never use the pom from the reactor, and the reactor order will not reorder parent before children. See https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ParentPOMResolution Please correct me if I am wrong. Regards, Julien De : Stephen Connolly stephen.alan.conno...@gmail.com À : Maven Users List users@maven.apache.org Envoyé le : Lundi 22 Août 2011 16h16 Objet : Re: Reactor doesn't build parent poms first? On 22 August 2011 14:37, Laird Nelson ljnel...@gmail.com wrote: On Mon, Aug 22, 2011 at 7:48 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Should have mentioned I was talking about SNAPSHOTs; sorry. Does that change the picture? Nope. Just to be clear, then: You're saying that in a multimodule project, where my root pom.xmlaggregates several submodules, and where one of those submodules is a pom.xml that serves as a parent to some other submodules--you're saying that even when all these things are declared as version 1.0-SNAPSHOT, Maven will use the repo copy of the parent, even though the very reactor plan it is executing tells it that it should be building the most recent copy? Or, using the same letters that I used in my prior message's example, if A, B and C are all 1.0-SNAPSHOT, and the version of B deployed to the repository is 75 days old, Maven will begin a full build from the root (A) by first scanning the module paths to see what projects are there (A, B and C), and because C references B as a parent, the 75-day-old copy of B will be retrieved from the (local) repo rather than Maven realizing that B is in the reactor plan as a module in its own right? No I am saying that if C references B 0.9-SNAPSHOT as its parent then the reactor will not require B 1.0-SNAPSHOT (from the reactor) to be built before C 1.0-SNAPSHOT. If the parent GAV is present in the reactor, then that is what will be used if the parent GA is present in the reactor only with a different V, then you might be lucky and see a warning if the relativePath points to it, otherwise Maven will not see an issue as long as the requested GAV is in a repo Best, Laird -- http://about.me/lairdnelson - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release plugin tagging with -SNAPSHOT
Hi, We are facing the same issue. This is a regression since last release of m-release-p. The proposed tag name contains a -SNAPSHOT. http://jira.codehaus.org/browse/MRELEASE-697 Regards, Julien - Mail original - De : Barrie Treloar baerr...@gmail.com À : Maven Users List users@maven.apache.org Cc : Envoyé le : Jeudi 28 Juillet 2011 8h30 Objet : Re: release plugin tagging with -SNAPSHOT On Thu, Jul 28, 2011 at 1:46 PM, Benson Margulies bimargul...@gmail.com wrote: Never mind this here, I isolated this to 2.2 and made a JIRA. Can you post the Jira so I can look at the summary of the problem please? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven API: how to get reactor order
Hi, Background: I'm trying to develop a release helper tool for my company. We can't use the maven-release-plugin for several reasons. We have a notion that is like a release train were several projects must be released at the same time. These projects can be Maven multi-module projects. These projects can have interdependencies (SNAPSHOT). But of course no SNAPSHOT dependency is allowed on a project that is not in the release train. Basically, I'm trying to have a tool to replace the current manual process: 1) think about release order according to inter dependencies (cycles are forbidden) 2) mvn release:prepare release:perform on first project 3) update all references to this project (replace SNAPSHOT version by released version) in all pom of the release train 4) mvn release:prepare release:perform on second project 5) update all references to this project (replace SNAPSHOT version by released version) in all pom of the release train ... (repeat for all projects of the train) We already have a tweak to allow a full build of the release train with one Maven command. We have a tool that create a Maven aggregator pom where each submodule is a svn:externals linking to the trunk of each project. pom.xml (aggregator) project1 - svn:externals to another_location/project1/trunk project2- svn:externals to another_location/project2/trunk ... projectN- svn:externals to another_location/projectN/trunk Now I try to do step 1 automatically. I want to find release order based on inter dependencies of my release train. I found the ProjectSorter class in Maven API, but it seems I have to create a MavenProject for each project, and each sub module (as it seems this is not recursive). Is there a better way ? In fact the best would be to create a graph of interdependencies. Because I would also try to detect and prevent this kind of cycle: project1/submodule1 depend on project2/submodule1 project2/submodule1 depend on project1/submodule2 Thanks for any pointer. Julien - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven API: how to get reactor order
I have just tested to be sure and it works (Maven 3.0.3): [INFO] Reactor Summary: [INFO] [INFO] module-1 .. SUCCESS [0.471s] [INFO] module-1-2 SUCCESS [2.141s] [INFO] module-2 .. SUCCESS [0.007s] [INFO] module-2-1 SUCCESS [1.116s] [INFO] module-1-1 SUCCESS [0.751s] [INFO] aggregator SUCCESS [0.005s] [INFO] [INFO] BUILD SUCCESS aggregator/pom.xml - module-1/pom.xml --- module-1-1/pom.xml --- module-1-2/pom.xml - module-2/pom.xml --- module-2-1/pom.xml 1-1 depends on 2-1 2-1 depends on 1-2 Anyway I want to detect and prevent this case. In my organisation module-1 and module-2 would be top level projects that have their own trunk/tag/branch. Going back to my question: which API can I use to get the reactor order, or better the reactor graph. Thanks Julien - Mail original - De : Ron Wheeler rwhee...@artifact-software.com À : users@maven.apache.org Cc : Envoyé le : Vendredi 22 Juillet 2011 13h07 Objet : Re: Maven API: how to get reactor order On 22/07/2011 4:08 AM, Julien HENRY wrote: Hi, Background: I'm trying to develop a release helper tool for my company. We can't use the maven-release-plugin for several reasons. We have a notion that is like a release train were several projects must be released at the same time. These projects can be Maven multi-module projects. These projects can have interdependencies (SNAPSHOT). But of course no SNAPSHOT dependency is allowed on a project that is not in the release train. Basically, I'm trying to have a tool to replace the current manual process: 1) think about release order according to inter dependencies (cycles are forbidden) 2) mvn release:prepare release:perform on first project 3) update all references to this project (replace SNAPSHOT version by released version) in all pom of the release train 4) mvn release:prepare release:perform on second project 5) update all references to this project (replace SNAPSHOT version by released version) in all pom of the release train ... (repeat for all projects of the train) We already have a tweak to allow a full build of the release train with one Maven command. We have a tool that create a Maven aggregator pom where each submodule is a svn:externals linking to the trunk of each project. pom.xml (aggregator) project1 - svn:externals to another_location/project1/trunk project2- svn:externals to another_location/project2/trunk ... projectN- svn:externals to another_location/projectN/trunk Now I try to do step 1 automatically. I want to find release order based on inter dependencies of my release train. I found the ProjectSorter class in Maven API, but it seems I have to create a MavenProject for each project, and each sub module (as it seems this is not recursive). Is there a better way ? In fact the best would be to create a graph of interdependencies. Because I would also try to detect and prevent this kind of cycle: project1/submodule1 depend on project2/submodule1 project2/submodule1 depend on project1/submodule2 Can you explain how this would come about. I do not see how this is possible, You would never get the projects to build as SNAPSHOTs in the first place. Ron Thanks for any pointer. Julien - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven API: how to get reactor order
So you must have version 5.1 of project 1-1 depending on version 5.0 of project 2-1 and version 5.1 of 2-1 depending on 5.0 of project 1-2? No, Maven is able to build even when all have the same version. See attached test project. But I would like to prevent users of doing so. Is that what you are trying to detect? My initial wish is to find automatically which one of module-1 or module-2 I should release first. Bonus is to detect cycles that could prevent the release. A better way to fix the problem is to use Maven properties to specify the versions of the project Then project 2-1 and 1-1 would be version myproject.version and would depend on myproject.version of each other. Maybe my previous message was not clear enough: module-1 and module-2 are separate projects with their own versions. They are not always released together, but only when they are integrated in the same release train. The aggregator project is created artificially in SVN using svn:externals. This allow to do a full build with a single Maven command execution. Screwing with Maven and writing plug-ins to fix this, is the hard way to solve a simple problem. I don't think this is a simple problem... ;) - Mail original - De : Ron Wheeler rwhee...@artifact-software.com À : users@maven.apache.org Cc : Envoyé le : Vendredi 22 Juillet 2011 15h06 Objet : Re: Maven API: how to get reactor order So you must have version 5.1 of project 1-1 depending on version 5.0 of project 2-1 and version 5.1 of 2-1 depending on 5.0 of project 1-2? Is that what you are trying to detect? A better way to fix the problem is to use Maven properties to specify the versions of the project Then project 2-1 and 1-1 would be version myproject.version and would depend on myproject.version of each other. Then, when you changed the value of myproject.version, the build would break at that instant and you could fix it. Screwing with Maven and writing plug-ins to fix this, is the hard way to solve a simple problem. Ron On 22/07/2011 8:28 AM, Julien HENRY wrote: I have just tested to be sure and it works (Maven 3.0.3): [INFO] Reactor Summary: [INFO] [INFO] module-1 .. SUCCESS [0.471s] [INFO] module-1-2 SUCCESS [2.141s] [INFO] module-2 .. SUCCESS [0.007s] [INFO] module-2-1 SUCCESS [1.116s] [INFO] module-1-1 SUCCESS [0.751s] [INFO] aggregator SUCCESS [0.005s] [INFO] [INFO] BUILD SUCCESS aggregator/pom.xml - module-1/pom.xml --- module-1-1/pom.xml --- module-1-2/pom.xml - module-2/pom.xml --- module-2-1/pom.xml 1-1 depends on 2-1 2-1 depends on 1-2 Anyway I want to detect and prevent this case. In my organisation module-1 and module-2 would be top level projects that have their own trunk/tag/branch. Going back to my question: which API can I use to get the reactor order, or better the reactor graph. Thanks Julien - Mail original - De : Ron Wheelerrwhee...@artifact-software.com À : users@maven.apache.org Cc : Envoyé le : Vendredi 22 Juillet 2011 13h07 Objet : Re: Maven API: how to get reactor order On 22/07/2011 4:08 AM, Julien HENRY wrote: Hi, Background: I'm trying to develop a release helper tool for my company. We can't use the maven-release-plugin for several reasons. We have a notion that is like a release train were several projects must be released at the same time. These projects can be Maven multi-module projects. These projects can have interdependencies (SNAPSHOT). But of course no SNAPSHOT dependency is allowed on a project that is not in the release train. Basically, I'm trying to have a tool to replace the current manual process: 1) think about release order according to inter dependencies (cycles are forbidden) 2) mvn release:prepare release:perform on first project 3) update all references to this project (replace SNAPSHOT version by released version) in all pom of the release train 4) mvn release:prepare release:perform on second project 5) update all references to this project (replace SNAPSHOT version by released version) in all pom of the release train ... (repeat for all projects of the train) We already have a tweak to allow a full build of the release train with one Maven command. We have a tool that create a Maven aggregator pom where each submodule is a svn:externals linking to the trunk of each project. pom.xml (aggregator) project1 - svn:externals to another_location/project1/trunk project2- svn:externals
Synchro issue between codehaus and central?
Hi, I have a problem using org.codehaus.sonar-plugins.pdf-report:maven-pdfreport-plugin:1.2. Nexus refuses to download the pom because md5 checksum doesn't match. I did some tests, and here are my results: Central [1] : - md5sum computed on downloaded pom = cd3e130dd8aee58484e1ab6d1817f0e0 - in .md5 file = 4b720e4669f09b336e08abe34b2bf546 Codehaus [2] : - md5sum computed ondownloaded pom = c9181c76ae57cdd343a8f65a95f94c58 - in .md5 file = 4a932f26a7904e187b53d92c7ccdaca5 According to modification date I suspect the codehaus file was re uploaded after the synchro was done on central. Does it mean codehaus allow redeploy of released artifacts? Can you confirm the md5 in .md5 files are wrong (it could be a bad joke of my corporate proxy) and if this is the case can someone fix it on central. The diff between the poms from central and codehaus show only a difference on the spanish í vs i: diff maven-pdfreport-plugin-1.2.pom maven-pdfreport-plugin-1.2-codehaus.pom 5c5 * Copyright (C) 2010 klicap - ingeniería del puzle --- * Copyright (C) 2010 klicap - ingenieria del puzle 123c123 Developed-byklicap - ingeniería del puzle/Developed-by --- Developed-byklicap - ingenieria del puzle/Developed-by I will try to download the JAR and check if they are the same. Regards, [1] http://repo1.maven.org/maven2/org/codehaus/sonar-plugins/pdf-report/maven-pdfreport-plugin/1.2/ [2] http://repository.codehaus.org/org/codehaus/sonar-plugins/pdf-report/maven-pdfreport-plugin/1.2/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: breaking backwards compatibility
Hi, This problem is not specific to Maven, but this is a Java issue. Running javac on P with -classpath=A.jar, B.jar, X-2.0.jar, X-1.0.jar will not work nor -classpath=A.jar, B.jar, X-1.0.jar, X-2.0.jar If you want to be able to use two versions of the same class side by side... you have to rename package/or class name (eg: com.acme.x1.TheClass and com.acme.x2.TheClass). Translated to Maven it means you will have different artifacts: com.acme:X:1.0 and com.acme:X2:1.0. P - A - X2 1.0 - B - X 1.0 This is how it works in Linux distributions with packages management. As long as a package is a replacement for another you can simply change version. But if you want to keep ability to use two artifacts at the same time = change artifactId. Here is an example from my distrib: S | Name | Type | Version | Arch | Repo --+--++--++-- | libdb_java-4_5 | paquet | 4.5.20-108.2 | x86_64 | openSUSE-11.4-Oss | libdb_java-4_8 | paquet | 4.8.30-2.2 | x86_64 | openSUSE-11.4-Oss My advice is to avoid this situation as it leads to a big mess. In some situation you may want to use maven-shade-plugin as a workaround [1]. Regards, Julien [1] http://maven.apache.org/plugins/maven-shade-plugin/examples/class-relocation.html - Message d'origine De : Tom Eugelink t.eugel...@knowledgeplaza.nl À : Maven Users List users@maven.apache.org Envoyé le : Mer 13 avril 2011, 13h 56min 06s Objet : Re: breaking backwards compatibility It is hard to make it clearer; suppose a version 2.0 of some library X got all @deprecated methods from 1.0 removed. A clean up. The project could have two dependencies that both refer to this library: P - A - X 2.0 - B - X 1.0 If this is resolved, then indeed X 2.0 is included, however B expects the 1.0 version and may be using a @deprecated method that is no longer present. The end project will crash. Is it possible to tell Maven that 2.0 is not a substitute for 1.0? On 13-4-2011 13:42, Benson Margulies wrote: There is perhaps a communications problem here. I don't think this is about ranges. I suspect that it is about: - project g:A version 1 depends on x:y:2.0 - project g:B version 1 depends on g:A:1 and x:y:1.0 What ends up in the classpath of B? x:y:2.0, I think. On Wed, Apr 13, 2011 at 7:17 AM, Schrecker, Wolfgang wolfgang.schrec...@atosorigin.com wrote: Maybe http://maven.apache.org/enforcer/enforcer-rules/index.html could help. Wolfgang -Ursprüngliche Nachricht- Von: Jörg Schaible [mailto:joerg.schai...@scalaris.com] Gesendet: Mittwoch, 13. April 2011 11:55 An: users@maven.apache.org Betreff: Re: breaking backwards compatibility Hi Tom, Tom Eugelink wrote: I know Maven version management can be, ah, challenging, so I stick to Maven compatible versioning. Maybe not to the deepest level (1.0.0-b01), but surely in a very common accepted style (1.0). I am not having any problems with Maven using the wrong versions. My question is with how to tell Maven two releases are no longer compatible. So if one dependency uses 1.x and the other uses 2.x, and 2.x is declared not backwards compatible to 1.x, then Maven should either: 1. report a build error on a version conflict 2. or include both versions of the artifact. What means not compatible for a single artifact? If my application only uses a constant defined in some class, the dependency is only incompatible if this constant is no longer available, has a different type or a value that causes a failure situation in my own app. You can define real incompatibility only from the consumer side. So what could Maven actually report by default? - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Atos Worldline GmbH Hahnstraße 25 60528 Frankfurt/Main Germany Phone: +49 69/6657-1176 Fax: Mobile: mailto: wolfgang.schrec...@atosorigin.com http://www.atosworldline.com Geschäftsführer: Wolf Kunisch Aufsichtsratsvorsitzender: Didier Dhennin Sitz der Gesellschaft: Frankfurt/Main Handelsregister: Frankfurt/Main HRB 40 417 * * * * * * * * L E G A LD I S C L A I M E R * * * * * * * * This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail by error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a
Re: read password protected zip
I don't think so, Stackoverflow question is self explaining: http://stackoverflow.com/questions/166340/write-a-password-protected-zip-file-in-java a Have you seen the answer talking about zip4j? I haven't tested it but it seems it is 100% Java and Apache 2.0 license. It is probably not on central but can be added to your internal repo. http://www.lingala.net/zip4j/ Regards, Julie - Message d'origine De : Antonio Petrelli antonio.petre...@gmail.com À : Maven Users List users@maven.apache.org Envoyé le : Mer 13 avril 2011, 15h 54min 09s Objet : Re: read password protected zip 2011/4/13 johnny989 john_jul...@uhc.com Is there a package in Maven that can open/read password protected (non AES) large (4GB+) zip files? I've searched through the repository but I wasn't able to find one. I know there are other commercial options external to maven but my team needs a solution soon and we have access to maven already. I don't think so, Stackoverflow question is self explaining: http://stackoverflow.com/questions/166340/write-a-password-protected-zip-file-in-java a http://stackoverflow.com/questions/166340/write-a-password-protected-zip-file-in-java Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [M3] CheckStyle configuration file
Hi, Where is located checkstyle configuration? In reporting section or plugins[Management] section? Regards, Julien - Message d'origine De : cattox andresi...@pol.pt À : users@maven.apache.org Envoyé le : Jeu 17 mars 2011, 11h 04min 20s Objet : [M3] CheckStyle configuration file Hi all, I've been trying to configure checkstyle while using maven checkstyle plugin. The problem is my pom configuration seems to be completly ignored The corresponding pom section of my pom file looks like this: ... . org.apache.maven.plugins. maven-checkstyle-plugin. 2.6. . checkstyle-conf.xml. . ... and after running: mvn -X -e checkstyle:checkstyle the log file shows this: ... [DEBUG] RuntimeInstance successfully initialized. [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-checkstyle-plugin:2.6:checkstyle' with basic configurator -- [DEBUG] (f) cacheFile = D:\projectos\java\qre\target/checkstyle-cachefile [DEBUG] (f) configLocation = config/sun_checks.xml [DEBUG] (f) consoleOutput = false ... The parameter configLocation assumes the default value Does anyone have any idea of what I am doing wrong?? -- View this message in context: http://maven.40175.n5.nabble.com/M3-CheckStyle-configuration-file-tp3868434p3868434.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [M3] CheckStyle configuration file
FYI it is a change in Maven 3. Here are a few informations I found: In [1]: Configuration in the reporting section also applies if plugin goals are invoked individually. The converse is not true-- if you configure the plugin inside build, that configuration will NOT apply to reporting. In [2]: [...] plugin configuration in the reporting section no longer affects plugins in the build section of the POM. Users that employed this style of configuration will need to copy the desired configuration parameters for a plugin from the reporting section to the build section. Maybe [1] should be updated? [1] http://docs.codehaus.org/display/MAVENUSER/Reporting+Plugins [2] https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-SiteandReporting - Message d'origine De : Olivier Lamy ol...@apache.org À : Maven Users List users@maven.apache.org Cc : cattox andresi...@pol.pt Envoyé le : Jeu 17 mars 2011, 12h 13min 05s Objet : Re: [M3] CheckStyle configuration file correct. 2011/3/17 cattox andresi...@pol.pt: I think I might have discovered the logic of it. By configuring it in the plugins section I'm configuring the checkstyle:checkstyle cmd. By configuring it in the reporting section I'm configuring the site cmd. Is that right? -- View this message in context: http://maven.40175.n5.nabble.com/M3-CheckStyle-configuration-file-tp3868434p3871359.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Unable to get the mvn release:prepare work
Hi, Can you run svn status in your project folder (I asume you are using SVN). Regards, Julien - Message d'origine De : ravi_atluri raviteja.atl...@gmail.com À : users@maven.apache.org Envoyé le : Lun 7 février 2011, 21h 39min 11s Objet : Re: Unable to get the mvn release:prepare work Hi Anders, I have locally modified files which I committed to my repository but still I get this. Thanks. On 7 February 2011 12:34, Anders Hammar [via Maven] ml-node+3374881-938815243-147...@n5.nabble.com wrote: You have locally modified files? The release plugin checks that all files are in sync with scm. More info at [1]. /Anders [1] http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html On Mon, Feb 7, 2011 at 21:07, ravi_atluri [hidden email]http://user/SendEmail.jtp?type=nodenode=3374881i=0 wrote: Hi when I am trying to run the mvn release:prepare for my project it is giving me this error: [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Cannot prepare the release because you have local modifications : [Accounts/pom.xml:modified] [Storage-Web/pom.xml:modified] [Product/pom.xml:modified] [Personalization/pom.xml:modified] [SocialNetworking/pom.xml:modified] [DeviceLogs/pom.xml:modified] [Community/pom.xml:modified] [LogAnalysis/pom.xml:modified] [DB/pom.xml:modified] [AddrBook/pom.xml:modified] [UsageLogs/pom.xml:modified] [Render-Web/pom.xml:modified] [pom.xml:modified] [QA/Web-PerformanceTests/pom.xml:modified] [QA/Web-IntegrationTests/pom.xml:modified] Any help would be greatly appreciated. Thanks. -- View this message in context: http://maven.40175.n5.nabble.com/Unable-to-get-the-mvn-release-prepare-work-tp3374840p3374840.htmlhttp://maven.40175.n5.nabble.com/Unable-to-get-the-mvn-release-prepare-work-tp3374840p3374840.html?by-user=t Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=3374881i=1 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=3374881i=2 -- If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Unable-to-get-the-mvn-release-prepare-work-tp3374840p3374881.html To unsubscribe from Unable to get the mvn release:prepare work, click herehttp://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=3374840code=cmF2aXRlamEuYXRsdXJpQGdtYWlsLmNvbXwzMzc0ODQwfDEyOTM0NjQzMDg=. -- View this message in context: http://maven.40175.n5.nabble.com/Unable-to-get-the-mvn-release-prepare-work-tp3374840p3374890.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : how to patch releases
Hi, I guess one has to create a branch from the tagged version. Then the version in the poms have to be set to 1.1.1-SNAPSHOT and then development starts. Also don't forget to update the scm section of your pom. Your description of the process is good, but I don't know if there is a fully automated way (there is release:branch but AFAIK this is to create a branch from trunk, not a branch from tag). And how about releasing it ? Can I use the release plugin again ? does it understand that in the scm tag there is now branches/xxx instead of trunk ? Yes, release plugin works fine. Regards, Julien - Message d'origine De : mremerson...@aim.com mremerson...@aim.com À : users@maven.apache.org Envoyé le : Jeu 13 janvier 2011, 13h 42min 01s Objet : how to patch releases Hi all, this might be a simple one and if there is documentation about it I'm happy to read that. Its a basic understanding question: I have a maven project and do a release - lets say 1.1 The maven release plugin manipulates the poms and tags the software in the scm. the trunk itself has e.g. 1.2-SNAPSHOT - everything is fine and the release is done How is the procedure if one needs to patch 1.1 to 1.1.1 ? I guess one has to create a branch from the tagged version. Then the version in the poms have to be set to 1.1.1-SNAPSHOT and then development starts. Is this process only doable by hand or is there also maven tools for that ? And how about releasing it ? Can I use the release plugin again ? does it understand that in the scm tag there is now branches/xxx instead of trunk ? is it the same procedure ? Thanks for any clarification or any link Emerson - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : How to write a plugin that generates source files based on the source in the project?
Hi, You should try to use new JDK 1.6 annotation processor utilities. The only constraint I see is that each class you want to parse must be annotated. Regards, Julien - Message d'origine De : Lewis, Eric eric.le...@ipi.ch À : users@maven.apache.org users@maven.apache.org Envoyé le : Jeu 13 janvier 2011, 16h 48min 14s Objet : How to write a plugin that generates source files based on the source in the project? Hi I'm trying to write a plugin which does the following: - Check the classes in the project and keep all classes that implement interface X. - For all X, get the fields, and if a field has a certain annotation, generate a class containing some constant information. Normally the plugin should be bound to the phase 'generate-sources'. However, the classes of the project aren't compiled yet at that moment, so I can't just get them from the classpath, right? Does anyone have a good idea or pointers how to do this correctly? Thanks best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Issue with Maven WAR plugin and overlay when using war:inplace
I will try your suggestion but according to the documentation, my use case should be the default one (without configuration). In addition, war:exploded produces the correct result but war:inplace produces a different result so I definitely think there is an issue. Regards, Julien - Message d'origine De : Kumar Ampani amp...@gmail.com À : Maven Users List users@maven.apache.org Envoyé le : Jeu 22 juillet 2010, 0h 11min 51s Objet : Re: Issue with Maven WAR plugin and overlay when using war:inplace Use overlay tags in war plugin configuration to control the order. On Wednesday, July 21, 2010, Julien HENRY henr...@yahoo.fr wrote: Hi all, I have a web application that depends on another WAR (overlay). According to m-war-p documentation [1], the current application is priority #1 and then come dependent war. My understanding is that when there are two files with same path in both current application and dependent war, this is the file in current application that should ultimately be taken to produce the final war. Example: current application contains the file src/main/webapp/WEB-INF/web.xml dependent war contain a nearly empty file dependentWar.war!WEB-INF/web.xml When I run mvn war:inplace I can read in the log: [INFO] --- maven-war-plugin:2.1-beta-1:inplace (default-cli) @ myWebApp --- ... [INFO] Processing war project [INFO] Processing overlay[ id com.mycompany:dependentWar] ... [INFO] File[WEB-INF/web.xml] belonged to overlay[currentBuild] so it will be overwritten. As a result the src/main/webapp/WEB-INF/web.xml file was overwritten in the current application by the file coming from the dependent WAR. If I run mvn war:exploded the result is correct and the file in target/myCurrentWebApp-XX-SNAPSHOT/WEB-INF/web.xml is the one coming from the current web app. Is it a known issue? Do you know if there is a workaround? Regards, Julien [1] http://maven.apache.org/plugins/maven-war-plugin/overlays.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Issue with Maven WAR plugin and overlay when using war:inplace
Hi all, I have a web application that depends on another WAR (overlay). According to m-war-p documentation [1], the current application is priority #1 and then come dependent war. My understanding is that when there are two files with same path in both current application and dependent war, this is the file in current application that should ultimately be taken to produce the final war. Example: current application contains the file src/main/webapp/WEB-INF/web.xml dependent war contain a nearly empty file dependentWar.war!WEB-INF/web.xml When I run mvn war:inplace I can read in the log: [INFO] --- maven-war-plugin:2.1-beta-1:inplace (default-cli) @ myWebApp --- ... [INFO] Processing war project [INFO] Processing overlay[ id com.mycompany:dependentWar] ... [INFO] File[WEB-INF/web.xml] belonged to overlay[currentBuild] so it will be overwritten. As a result the src/main/webapp/WEB-INF/web.xml file was overwritten in the current application by the file coming from the dependent WAR. If I run mvn war:exploded the result is correct and the file in target/myCurrentWebApp-XX-SNAPSHOT/WEB-INF/web.xml is the one coming from the current web app. Is it a known issue? Do you know if there is a workaround? Regards, Julien [1] http://maven.apache.org/plugins/maven-war-plugin/overlays.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Issue with Maven WAR plugin and overlay when using war:inplace
I have created an issue in JIRA with an attached it: http://jira.codehaus.org/browse/MWAR-229 Regards, Julien - Message d'origine De : Julien HENRY henr...@yahoo.fr À : users@maven.apache.org Envoyé le : Mer 21 juillet 2010, 12h 17min 00s Objet : Issue with Maven WAR plugin and overlay when using war:inplace Hi all, I have a web application that depends on another WAR (overlay). According to m-war-p documentation [1], the current application is priority #1 and then come dependent war. My understanding is that when there are two files with same path in both current application and dependent war, this is the file in current application that should ultimately be taken to produce the final war. Example: current application contains the file src/main/webapp/WEB-INF/web.xml dependent war contain a nearly empty file dependentWar.war!WEB-INF/web.xml When I run mvn war:inplace I can read in the log: [INFO] --- maven-war-plugin:2.1-beta-1:inplace (default-cli) @ myWebApp --- ... [INFO] Processing war project [INFO] Processing overlay[ id com.mycompany:dependentWar] ... [INFO] File[WEB-INF/web.xml] belonged to overlay[currentBuild] so it will be overwritten. As a result the src/main/webapp/WEB-INF/web.xml file was overwritten in the current application by the file coming from the dependent WAR. If I run mvn war:exploded the result is correct and the file in target/myCurrentWebApp-XX-SNAPSHOT/WEB-INF/web.xml is the one coming from the current web app. Is it a known issue? Do you know if there is a workaround? Regards, Julien [1] http://maven.apache.org/plugins/maven-war-plugin/overlays.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Running antrun plugin twice in same phase with another plugin in between?
Hi, Have you tried the following configuration? build plugins plugin artifactIdmaven-antrun-plugin/artifactId executions execution idtask1/id phaseyourphase/phase configuration tasks !-- Some task -- /tasks /configuration goals goalrun/goal /goals /execution /executions /plugin plugin artifactIdyour middle plugin/artifactId executions execution idtask2/id phaseyourphase/phase configuration ... /configuration goals ... /goals /execution /executions /plugin plugin artifactIdmaven-antrun-plugin/artifactId executions execution idtask3/id phaseyourphase/phase configuration tasks !-- Some other task -- /tasks /configuration goals goalrun/goal /goals /execution /executions /plugin /plugins /build I have not tested so I'm not sure it will work. Regards, Julien - Message d'origine De : Wim Deblauwe wim.debla...@gmail.com À : Maven Users List users@maven.apache.org Envoyé le : Mar 13 juillet 2010, 11h 09min 36s Objet : Running antrun plugin twice in same phase with another plugin in between? Hi, I need to run the antrun plugin twice in the packaging phase. I found this on the wiki: http://docs.codehaus.org/display/MAVENUSER/MiniGuide-AntMultiPhase However, it speaks of different lifecycle phases. I tried with the same phase and that works, however, I need to run another plugin in between. Is this possible? I was hoping that all plugins' executions would be sorted by their id. That way, i could use id's like 'step-1-do-something', 'step-2-do-something-else', to force a certain order of plugin execution. regards, Wim - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : m2Eclipse
Hi, You should install subclipse using this update site: http://subclipse.tigris.org/update_1.6.x Regards, Julien - Message d'origine De : Greg Akins angryg...@gmail.com À : Maven Users List users@maven.apache.org Envoyé le : Jeu 3 juin 2010, 15h 36min 09s Objet : m2Eclipse I just installed the m2Eclipse plugin and am trying to checkout a file from Subversion. Getting this error SCM provider is not available for scm:null... Googling a bit led to suggestions that I didn't have the Subversion SCM provider installed, but I'm not seeing that in the list of available software from the Sonatype update site. Can anyone tell me what I'm missing? -- Greg Akins href=http://insomnia-consulting.org; target=_blank http://insomnia-consulting.org target=_blank http://www.pghcodingdojo.org href=http://pittjug.dev.java.net; target=_blank http://pittjug.dev.java.net target=_blank http://twitter.com/akinsgre href=http://www.linkedin.com/in/akinsgre; target=_blank http://www.linkedin.com/in/akinsgre - To unsubscribe, e-mail: href=mailto:users-unsubscr...@maven.apache.org;users-unsubscr...@maven.apache.org For additional commands, e-mail: href=mailto:users-h...@maven.apache.org;users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Organization of interdepending projects and super projects
Hi,
Concerning your problem number 1, here is the clean solution:
1) package the tests of your projectCommon in a projectCommon-XX-tests.jar
2) add a dependency in projectSpec_1 and projectSpec_2 with type=test-jar
and scope=test
Read : http://maven.apache.org/guides/mini/guide-attached-tests.html for details
Regards,
Julien
- Message d'origine
De : oor o...@suss.no
À : users@maven.apache.org
Envoyé le : Jeu 3 juin 2010, 15h 16min 24s
Objet : Organization of interdepending projects and super projects
1)
The following problem is a part problem of the problem in 2)
I have
three
projects:
projectSpec_1
projectSpec_2
projectCommon
projectSpec_1
depends on projectCommon during all phases
projectSpec_2 depends on
projectCommon during all phases
projectCommon has its own tests, using
general test utilities contained in
its test sources
projectSpec_1 has its
own tests, using general test utilities contained in
projectCommon's test
sources
projectSpec_2 has its own tests, using general test utilities
contained in
projectCommon's test sources
This gave me problems when
running tests in projectSpec_1 and projectSpec_2:
Their test sources could
not be compiled,
as projectCommon's test sources were not
available for
the test compile.
I solved this in the following way in e.g.
projectSpec_1's pom.xml:
...
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuild-helper-maven-plugin/artifactId
version1.5/version
executions
execution
idadd-test-resource/id
phasegenerate-test-resources/phase
goals
goaladd-test-resource/goal
/goals
configuration
resources
resource
directory${basedir}/../projectCommon/target/test-classes/directory
/resource
/resources
/configuration
/execution
/executions
/plugin
...
It works, but I have the
strong feeling this is best described as a hack,
not adhering to best
practices of Maven 2.
I guess my project is organized in a non-optimal
way.
One indication is that the projectSpec_1's pom.xml is dependent on
the
physical
directory placement of the projectCommon
project.
2)
The same projects as above, with the additional
information:
I have two super-projects in addition to
1):
ProjectSuper_1 consists of projectSpec_1, projectSpec_2 and
projectCommon
projectSpec_1 depends on projectCommon during all
phases
projectSpec_2 depends on projectCommon during all
phases
projectCommon
ProjectSuper_2 consists of projectSpec_1,
projectSpec_3 and projectCommon
projectSpec_1 depends on projectCommon during
all phases
projectSpec_3 depends on projectCommon during all
phases
projectCommon
I am not convinced parent-child inheritage is
part of a correct solution,
as a project can only have one
parent.
projectCommon cannot inherit ProjectSuper_1 and
ProjectSuper_2
projectSpec_1 cannot inherit ProjectSuper_1 and
ProjectSuper_2
3)
I also experience inconveniences when doing the
coding, as organized just
now.
When working on ProjectSuper_1 (or
ProjectSuper_2 for that sake), I code in
source belonging
to
projectSpec_1, projectSpec_2 and projectCommon at the same time. To
compile
projectSpec_1,
I then first have to compile and install projectCommon, to
expose its
correct snapshot for projectSpec_1.
To achieve this, I have
made som DOS bat files, that first installs
projectCommon
and thereafter
compiles (and possibly installs) projectSpec_1. Using command
files
to
help me out of the problems occur to me as a
defeat.
Conclusion:
===
I am fairly new to Maven2, so I
have not quite got learned how to
adhere to the Maven2 best
practices.
Please give me a hint (or better: more than just a hint) what I
should do
differently
to origanize my projects better.
--
View this
message in context:
href=http://old.nabble.com/Organization-of-interdepending-projects-and-super-projects-tp28767294p28767294.html;
target=_blank
http://old.nabble.com/Organization-of-interdepending-projects-and-super-projects-tp28767294p28767294.html
Sent
from the Maven - Users mailing list archive at
Nabble.com.
-
To
unsubscribe, e-mail:
href=mailto:users-unsubscr...@maven.apache.org;users-unsubscr...@maven.apache.org
For
additional commands, e-mail:
href=mailto:users-h...@maven.apache.org;users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Add an argument to jar plugin
Hi, I would like to add a parameter to the execution of the jar command: -J-Dsun.misc.JarIndex.metaInfFilenames=true (see: http://bugs.sun.com/view_bug.do?bug_id=2183678) Reading the doc of m-jar-p I don't see a way to do that. Do you know if this is possible to give argument to the jar command like for the compiler plugin? Thanks Julien - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Add an argument to jar plugin
Thanks Stephen. I will contribute a patch to add a parameter to maven-archiver and plexus-archiver. This parameter will be named indexMetaInfFilenames and will have the same behavior than -Dsun.misc.JarIndex.metaInfFilenames=true in Sun JDK 1.6.0_18+. Regards, Julien - Message d'origine De : Stephen Connolly stephen.alan.conno...@gmail.com À : Maven Users List users@maven.apache.org Envoyé le : Lun 31 mai 2010, 12h 11min 28s Objet : Re: Add an argument to jar plugin That would be because maven-jar-plugin does _not_ fork the jar command but builds the jar itself On 31 May 2010 11:00, Julien HENRY ymailto=mailto:henr...@yahoo.fr; href=mailto:henr...@yahoo.fr;henr...@yahoo.fr wrote: Hi, I would like to add a parameter to the execution of the jar command: -J-Dsun.misc.JarIndex.metaInfFilenames=true (see: target=_blank http://bugs.sun.com/view_bug.do?bug_id=2183678) Reading the doc of m-jar-p I don't see a way to do that. Do you know if this is possible to give argument to the jar command like for the compiler plugin? Thanks Julien - To unsubscribe, e-mail: href=mailto:users-unsubscr...@maven.apache.org;users-unsubscr...@maven.apache.org For additional commands, e-mail: href=mailto:users-h...@maven.apache.org;users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Issue with release plugin and javasvn provider
Hi,
I'm trying to use javasvn provider with the release plugin. But it seems there
is an issue as scmCommentPrefix is not taken into account during tagging. Can
someone check my configuration and then tell me if I did something wrong or if
I should report a bug (bug fore release plugin? scm-api? svnjava provider?)
I have configured my pom like this:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.0/version
configuration
providerImplementations
svnjavasvn/svn
/providerImplementations
/configuration
dependencies
dependency
groupIdcom.google.code.maven-scm-provider-svnjava/groupId
artifactIdmaven-scm-provider-svnjava/artifactId
version1.10/version
/dependency
/dependencies
/plugin
In my organisation we need to provide a specific comment during any svn write
operation (commit, tag) so I am using -DscmCommentPrefix option:
mvn release:prepare -DscmCommentPrefix=[XYZ]
The commit in trunk was done successfully but the tag failed:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-release-plugin:2.0:prepare' with basic
configurator --
[DEBUG] (f) addSchema = true
[DEBUG] (f) allowReleasePluginSnapshot = false
[DEBUG] (f) allowTimestampedSnapshots = false
[DEBUG] (f) autoVersionSubmodules = true
[DEBUG] (s) basedir = D:\myproject
[DEBUG] (f) commitByProject = false
[DEBUG] (f) dryRun = false
[DEBUG] (f) generateReleasePoms = false
[DEBUG] (f) javaHome = C:\Program Files\Java\jdk1.6.0_20\jre
[DEBUG] (f) localCheckout = false
[DEBUG] (f) mavenExecutorId = invoker
[DEBUG] (f) mavenHome = D:\apache-maven-3.0-beta-1
[DEBUG] (f) preparationGoals = clean verify
[DEBUG] (f) project = MavenProject: com.mycompany:myproject:2.3.0 @
D:\myproject\pom.xml
[DEBUG] (f) providerImplementations = {svn=javasvn}
[DEBUG] (f) reactorProjects = [MavenProject: com.mycompany:myproject:2.3.0 @
D:\myproject\pom.xml]
[DEBUG] (f) remoteTagging = true
[DEBUG] (f) resume = true
[DEBUG] (f) scmCommentPrefix = [XYZ]
[DEBUG] (f) session = org.apache.maven.execution.mavensess...@bf7916
[DEBUG] (f) settings = org.apache.maven.execution.settingsadap...@1478a2d
[DEBUG] (f) updateDependencies = true
[DEBUG] (f) useEditMode = false
[DEBUG] -- end configuration --
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Resuming release from phase 'scm-tag'
[INFO] Tagging release with the label myproject-2.3.0...
[DEBUG] ScmTagPhase :: scmTagParameters remotingTag true
[DEBUG] ScmTagPhase :: scmTagParameters scmRevision null
[INFO] SVN checkout directory: D:\myproject
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5.109s
[INFO] Finished at: Fri May 21 12:01:10 CEST 2010
[INFO] Final Memory: 5M/15M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on
project myproject: Unable to tag SCM
Provider message:
SVN tag failed.
Command output:
svn: Commit failed (details follow):
svn: Commit blocked by pre-commit hook (exit code 1) with output:
Associations are required on commit.
Thanks
Julien
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Call to anyone using Maven 3 with webstart plugin
Hi all, I think I have spotted a bug with Maven 3 beta 1 and webstart plugin (dependencies are not added in the jnlp file). Before I try to create a test case, does anybody else facing the same issue? Regards, Julien - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AMP packaging type and cobertura
Hi all,
I have a project that is using Maven Alfresco integration [1] to produce AMP
artifacts. There is a new packaging type amp. Looking at the source code of
the plugin the language is java [2].
On cobertura side there is a check [3] to prevent instrumentation in case of
non java artifact:
ArtifactHandler artifactHandler = project.getArtifact().getArtifactHandler();
if ( !java.equals( artifactHandler.getLanguage() ) )
{
getLog().info(
Not executing cobertura:instrument as the project is not a Java
classpath-capable package );
}
As AMP is supposed to be a java artifact (and that's actually true) I was
expecting cobertura to perform instrumentation. But in fact it is not:
[INFO]
[INFO] Building My Project AMP Packaging
[INFO]task-segment: [org.codehaus.mojo:cobertura-maven-plugin:2.3:cobertura]
[INFO]
[INFO] Preparing cobertura:cobertura
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: 5 at timestamp: 1268819729587
[INFO] [nosnapshot:strip {execution: default}]
[INFO] Storing noSnapshotVersion: 0.1
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 8 resources to alfresco/module/fr.cirad.contrat
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [cobertura:instrument {execution: default-instrument}]
[INFO] Not executing cobertura:instrument as the project is not a Java
classpath-capable package
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory:
/var/lib/hudson/workspace/MyProject/trunk/target/surefire-reports
---
T E S T S
---
Running fr.myproject.contrat.CoreTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO] [cobertura:cobertura {execution: default-cli}]
[INFO] Not executing cobertura:report as the cobertura data file
(/var/lib/hudson/workspace/MyProject/trunk/target/cobertura/cobertura.ser)
could not be found
[WARN] Cobertura report not found at
/var/lib/hudson/workspace/MyProject/trunk/target/site/cobertura/coverage.xml
Do you have any idea of the problem? Does it come from AMP plugin, cobertura
plugin or Maven core?
Thanks
Julien
[1] http://wiki.alfresco.com/wiki/Managing_Alfresco_Lifecyle_with_Maven
[2]
http://maven-alfresco-archetypes.googlecode.com/svn/trunk/plugins/maven-amp-plugin/src/main/resources/META-INF/plexus/components.xml
[3]
http://svn.codehaus.org/mojo/tags/cobertura-maven-plugin-2.3/src/main/java/org/codehaus/mojo/cobertura/CoberturaInstrumentMojo.java
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Possible regression with Maven 3 alpha 7 (ejb manifest classpaht)
Hi, One project in my company is using Maven 3 and they have switched from alpha 6 to alpha 7. They told me there is a regression in their EJB modules. The generated manifest is supposed to contain the classpath with all dependencies. It was working fine previously but now it is empty. Are you already aware of such an issue or should I investigate? Regards, Julien - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Possible regression with Maven 3 alpha 7 (ejb manifest classpaht)
Done: http://jira.codehaus.org/browse/MNG-4596 - Message d'origine De : Anders Hammar and...@hammar.net À : Maven Users List users@maven.apache.org Envoyé le : Mer 17 mars 2010, 14 h 12 min 35 s Objet : Re: Possible regression with Maven 3 alpha 7 (ejb manifest classpaht) I don't find a jira filed for alpha-7 for this. Please create a project that reproduces this and file a jira at href=http://jira.codehaus.org/browse/MNG; target=_blank http://jira.codehaus.org/browse/MNG /Anders On Wed, Mar 17, 2010 at 13:36, Julien HENRY href=mailto:henr...@yahoo.fr;henr...@yahoo.fr wrote: Hi, One project in my company is using Maven 3 and they have switched from alpha 6 to alpha 7. They told me there is a regression in their EJB modules. The generated manifest is supposed to contain the classpath with all dependencies. It was working fine previously but now it is empty. Are you already aware of such an issue or should I investigate? Regards, Julien - To unsubscribe, e-mail: href=mailto:users-unsubscr...@maven.apache.org;users-unsubscr...@maven.apache.org For additional commands, e-mail: href=mailto:users-h...@maven.apache.org;users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Re : Possible regression with Maven 3 alpha 7 (ejb manifest classpaht)
Correct, many thanks to Benjamin for the fix and for releasing quickly. - Message d'origine De : Anders Hammar and...@hammar.net À : Maven Users List users@maven.apache.org Envoyé le : Mer 17 mars 2010, 21 h 14 min 55 s Objet : Re: Re : Possible regression with Maven 3 alpha 7 (ejb manifest classpaht) Ok, I now see that it's your issue that has been moved to the ejb plugin. I have to say that Benjamin is extremely quick on fixing things! /Anders On Wed, Mar 17, 2010 at 21:11, Anders Hammar href=mailto:and...@hammar.net;and...@hammar.net wrote: I just saw the vote for 2.2.1 of the ejb plugin and possibly your issue is related to the ejb plugin and not maven 3.0-alpha-7 itself: href=http://jira.codehaus.org/browse/MEJB-46; target=_blank http://jira.codehaus.org/browse/MEJB-46 /Anders On Wed, Mar 17, 2010 at 16:43, Julien HENRY href=mailto:henr...@yahoo.fr;henr...@yahoo.fr wrote: Done: href=http://jira.codehaus.org/browse/MNG-4596; target=_blank http://jira.codehaus.org/browse/MNG-4596 - Message d'origine De : Anders Hammar ymailto=mailto:and...@hammar.net; href=mailto:and...@hammar.net;and...@hammar.net À : Maven Users List href=mailto:users@maven.apache.org;users@maven.apache.org Envoyé le : Mer 17 mars 2010, 14 h 12 min 35 s Objet : Re: Possible regression with Maven 3 alpha 7 (ejb manifest classpaht) I don't find a jira filed for alpha-7 for this. Please create a project that reproduces this and file a jira at href= href=http://jira.codehaus.org/browse/MNG; target=_blank http://jira.codehaus.org/browse/MNG; target=_blank href=http://jira.codehaus.org/browse/MNG; target=_blank http://jira.codehaus.org/browse/MNG /Anders On Wed, Mar 17, 2010 at 13:36, Julien HENRY href=mailto: ymailto=mailto:henr...@yahoo.fr; href=mailto:henr...@yahoo.fr;henr...@yahoo.fr ymailto=mailto:henr...@yahoo.fr; href=mailto:henr...@yahoo.fr;henr...@yahoo.fr wrote: Hi, One project in my company is using Maven 3 and they have switched from alpha 6 to alpha 7. They told me there is a regression in their EJB modules. The generated manifest is supposed to contain the classpath with all dependencies. It was working fine previously but now it is empty. Are you already aware of such an issue or should I investigate? Regards, Julien - To unsubscribe, e-mail: href=mailto: ymailto=mailto:users-unsubscr...@maven.apache.org; href=mailto:users-unsubscr...@maven.apache.org;users-unsubscr...@maven.apache.org href=mailto:users-unsubscr...@maven.apache.org;users-unsubscr...@maven.apache.org For additional commands, e-mail: href=mailto: href=mailto:users-h...@maven.apache.org;users-h...@maven.apache.org ymailto=mailto:users-h...@maven.apache.org; href=mailto:users-h...@maven.apache.org;users-h...@maven.apache.org - To unsubscribe, e-mail: href=mailto:users-unsubscr...@maven.apache.org;users-unsubscr...@maven.apache.org For additional commands, e-mail: href=mailto:users-h...@maven.apache.org;users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : How to differentiate between pom.xml and ant's build file
Hi, You could try an XML validation using Maven XSD (http://maven.apache.org/maven-v4_0_0.xsd). If the validation is ok = this is a valid POM. If the validation is ko... it can be anything else. Regards, Julien - Message d'origine De : amaresh mourya amaresh.mou...@gmail.com À : Maven Users List users@maven.apache.org Envoyé le : Lun 8 Mars 2010, 11 h 40 min 05 s Objet : How to differentiate between pom.xml and ant's build file Hi All, I want to write a recognizer class which takes input any xml file and returns true or false based on , whether or not the xml is POM. Problem : Since Ant's build file and POM both have root element with/without Namespace. I don't want POM Name to be restricted to just pom.xml, this could be anything say myproj.xml etc. Still I want this myProj.xml to be recognized as POM with above Recognizer class. Can same one suggest me the conditions to differentiate between them. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Re : How to differentiate between pom.xml and ant's build file
Are you sure namespace is required to perform validation? What are you using? See http://java.sun.com/developer/technicalArticles/xml/validationxpath/ for an example of XSD validation. There is no namespace in the XML document. Regards, Julien - Message d'origine De : amaresh mourya amaresh.mou...@gmail.com À : Maven Users List users@maven.apache.org Envoyé le : Lun 8 Mars 2010, 12 h 18 min 14 s Objet : Re: Re : How to differentiate between pom.xml and ant's build file Hi All, Thanks for your replies. I tried validation with XSD(http://maven.apache.org/maven-v4_0_0.xsd).but It fails since the namespace is missing. I think any xml could still be POM if it doesn't have namespace as I have seen many pom.xml without schema. thanks Amaresh On Mon, Mar 8, 2010 at 4:32 PM, Julien HENRY wrote: Hi, You could try an XML validation using Maven XSD ( http://maven.apache.org/maven-v4_0_0.xsd). If the validation is ok = this is a valid POM. If the validation is ko... it can be anything else. Regards, Julien - Message d'origine De : amaresh mourya À : Maven Users List Envoyé le : Lun 8 Mars 2010, 11 h 40 min 05 s Objet : How to differentiate between pom.xml and ant's build file Hi All, I want to write a recognizer class which takes input any xml file and returns true or false based on , whether or not the xml is POM. Problem : Since Ant's build file and POM both have root element with/without Namespace. I don't want POM Name to be restricted to just pom.xml, this could be anything say myproj.xml etc. Still I want this myProj.xml to be recognized as POM with above Recognizer class. Can same one suggest me the conditions to differentiate between them. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Clean up of pom files
Hi, I have the same need and I have opened a Sonar feature request: http://jira.codehaus.org/browse/SONAR-1399 Read the comments to see the proposals. You can also look at http://maven.apache.org/developers/conventions/code.html#POM_Code_Convention to see Maven POM element ordering convention. Regards, Julien - Message d'origine De : Nick Stolwijk nick.stolw...@gmail.com À : Maven Users List users@maven.apache.org Envoyé le : Mer 24 Février 2010, 11 h 08 min 05 s Objet : Re: Clean up of pom files Thanks, that plugin looks promising! Only their default ordering is not my preferable ordering, but I can see it is configurable. :) Thanks, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Feb 24, 2010 at 10:48 AM, Anders Hammar wrote: You might want to use this plugin: http://code.google.com/p/sortpom/ /Anders On Wed, Feb 24, 2010 at 10:30, Nick Stolwijk wrote: Hi all, We have a multitude of components and projects all build with maven and we want to enforce some standard layout for the pom files, like the ordering of the elements(like the ordering in the schema) and forbidding some elements (like company and url, there are already set in the company pom). So 2 questions: - Is there a maven/eclipse/netbeans plugin which can sort pom (xml) files based on their schema? - Is there an enforcer plugin who can enforce the ordering of the elements and forbidding some elements. Hope someone can help, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : RCP
Hi, You can try Tycho plugins: http://tycho.sonatype.org/ Regards, Julien - Message d'origine De : Michael Hüttermann mich...@huettermann.net À : users@maven.apache.org Envoyé le : Lun 22 Février 2010, 13 h 28 min 11 s Objet : RCP Hello, what is the recent recommended way to build RCP apps? Is a how-to available which is up-to-date ? Thanks in advance. Michael - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Embedded error: Unknown artifact type[xml.zip]
Hi Stephane, I've mapped xml.zip custom type using this syntax: artifactTypeMappings artifactTypeMapping type=xml.zip mapping=jar/ /artifactTypeMappings The build is now able to terminate, but in my EAR file I can see all xml.zip files are packaged inside. So for me this is not a correct workaround. Regards, Julien - Message d'origine De : Stephane Nicoll stephane.nic...@gmail.com À : Maven Users List users@maven.apache.org Envoyé le : Mar 16 Février 2010, 23 h 08 min 40 s Objet : Re: Embedded error: Unknown artifact type[xml.zip] You can also map xml.zip in the plugin configuration if you want, which will avoid that useless message http://maven.apache.org/plugins/maven-ear-plugin/faq.html#har-files S. On Tue, Feb 16, 2010 at 5:02 PM, Julien HENRY wrote: Hi, One project I'm dealing with is bitten by an issue when assembling EAR artifact in a multi-module build. It seems the EAR plugin try to process a dependency that it should not see when building from parent project. The build is ok when building ear module alone. [INFO] Failed to initialize ear modules Embedded error: Unknown artifact type[xml.zip] I've created a short test case to reproduce the issue. The build fail when using Maven 2.2.1 but is successful when using Maven 3.0-alpha-6. Unfortunately the project will not be able to switch until Maven 3 is advertised as stable. 2 questions: - where do you think should I open the JIRA issue? In EAR plugin or Maven core? - do you think there is half a chance the bug may be fixed in 2.2.x branch? Regards, Julien - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck -- S.Yegge - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Embedded error: Unknown artifact type[xml.zip]
Hi, One project I'm dealing with is bitten by an issue when assembling EAR artifact in a multi-module build. It seems the EAR plugin try to process a dependency that it should not see when building from parent project. The build is ok when building ear module alone. [INFO] Failed to initialize ear modules Embedded error: Unknown artifact type[xml.zip] I've created a short test case to reproduce the issue. The build fail when using Maven 2.2.1 but is successful when using Maven 3.0-alpha-6. Unfortunately the project will not be able to switch until Maven 3 is advertised as stable. 2 questions: - where do you think should I open the JIRA issue? In EAR plugin or Maven core? - do you think there is half a chance the bug may be fixed in 2.2.x branch? Regards, Julien - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Embedded error: Unknown artifact type[xml.zip]
- where do you think should I open the JIRA issue? In EAR plugin or Maven core? If you think this is a bug in the EAR plugin, then open it there. In fact I guess it is somewhere in Maven core (something concerning dependency/classpath resolution in reactor build). The fact it works with Maven 3 tends to support this theory. But I would like a confirmation. Perhaps similar bug report already exists. - do you think there is half a chance the bug may be fixed in 2.2.x branch? If its simply a bug in a plugin, it seems more likely to be fixed (and sooner) than finding and fixing a bunch in 2.2.x. Yeah, that's what I believe too. I've recently started a thread about the current dilemma in corporate environment: Stable Maven 2 will certainly not receive major fix concerning this kind of bug (Maven 3 was actually written to clean dependency management). On the other hand Maven 3 is still flagged as alpha which prevents adoption in certain corporate projects. Thanks Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
${user.home} not substituted in settings.xml localRepository
Hi,
I'm bitten by the same issue that was already reported last september [1]. I'm
using Hudson with Maven 2.2.1 and I wrote:
localRepository${user.home}/repositories/${env.JOB_NAME}/repository/localRepository
but it doesn't work as ${user.home} is not correctly handled.
Is there already a JIRA issue opened?
According to [2]:
Java System Properties: All properties accessible via
java.lang.System.getProperties() are available as POM properties, such as
${java.home}.
Regards,
Julien
[1] http://www.mail-archive.com/users@maven.apache.org/msg102070.html
[2] http://maven.apache.org/settings.html
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re : ${user.home} not substituted in settings.xml localRepository
It seems to be fixed in Maven 3 alpha 6. Just have to wait for Hudson
supporting Maven 3...
- Message d'origine
De : Julien HENRY henr...@yahoo.fr
À : users@maven.apache.org
Envoyé le : Jeu 14 Janvier 2010, 11 h 08 min 59 s
Objet : ${user.home} not substituted in settings.xml localRepository
Hi,
I'm bitten by the same issue that was already reported last september [1].
I'm
using Hudson with Maven 2.2.1 and I wrote:
${user.home}/repositories/${env.JOB_NAME}/repository
but it doesn't work as ${user.home} is not correctly handled.
Is there already a JIRA issue opened?
According to [2]:
Java System Properties: All properties accessible via
java.lang.System.getProperties() are available as POM properties, such as
${java.home}.
Regards,
Julien
[1] http://www.mail-archive.com/users@maven.apache.org/msg102070.html
[2] http://maven.apache.org/settings.html
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re : Always active profiles
Hi, I suppose you are talking about profile defined in pom, otherwise you can look at activeProfiles section of settings.xml. Regards Julien - Message d'origine De : Mark Hobson markhob...@gmail.com À : Maven Users List users@maven.apache.org Envoyé le : Jeu 14 Janvier 2010, 12 h 04 min 19 s Objet : Always active profiles Hi there, Is there a better way of always activating a profile, unless explicitly deactivated, than using a dummy property activator? For example: !dummy I can't use activeByDefault since I want the profile to be activated even when other profiles in the pom are active. It could be worth introducing an always active activator, something like: I'll raise an issue if no-one objects. Cheers, Mark - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Transactional Behaviour Maven Modules
Hi, I have recently opened a wish [1] that is related (even if the title of the wish is not generic enough). In my proposal I called it an atomic deploy process for multimodule. But this is only a wish and I don't think such a feature exists (even in Maven 3). As a workaround, see the answer of Benjamin: use staging mechanism associated with a good MRM. Regards, Julien [1] http://jira.codehaus.org/browse/MDEPLOY-114 - Message d'origine De : Poyan Gerami poyan.gerami-kons...@folksam.se À : users@maven.apache.org Envoyé le : Mer 13 Janvier 2010, 11 h 07 min 40 s Objet : Transactional Behaviour Maven Modules Hello, I have an maven project with 3 modules. Each module deploy an jar archive file to my application server. I whant to get an transactional behvaiour when i deploy my 3 modules, i mean I whant eather none or all 3 modules get deployed. Today it can be like module 1 and 2 deploys to the server but module 3 does not deploy for some error in the test phase. Does maven have support for somthing like this ? / Poyan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Re : [ANN] Maven Compiler Plugin 2.1 Released
OK, thanks for the informations Stephen.
Regards,
Julien
- Message d'origine
De : Stephen Connolly stephen.alan.conno...@gmail.com
À : Maven Users List users@maven.apache.org
Envoyé le : Sam 2 Janvier 2010, 22 h 40 min 48 s
Objet : Re: Re : [ANN] Maven Compiler Plugin 2.1 Released
yes, whoever added the toolchains support did nit create a jira entry for the
feature.
as I see it there is one problem with toolchains, as implemented, namely it
is
not possible to scope multiple toolchains in the same project, eg production
uses jdk 1.4, test uses jdk 1.5
I intend to fix this issue and address it with a new version of all the
required
plugins, but first priority was getting a release out since the previous
release
was in 2007
Sent from my [rhymes with tryPod] ;-)
On 2 Jan 2010, at 18:58, Julien HENRY wrote:
Hi,
Is this version toolchains aware? This is not written in release notes and
the
page about toolchains [1] was not updated.
Regards,
Julien
[1] http://maven.apache.org/guides/mini/guide-using-toolchains.html
De : Stephen Connolly
À : annou...@maven.apache.org; Maven Users List
Cc : Maven Developers List
Envoyé le : Sam 2 Janvier 2010, 13 h 35 min 41 s
Objet : [ANN] Maven Compiler Plugin 2.1 Released
The Maven team is pleased to announce the release of the Maven
Compiler Plugin, version 2.1
This plugin is used to compile the sources of your project. .
http://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-compiler-plugin
2.1
Release Notes - Maven 2.x Compiler Plugin - Version 2.1
** Bug
* [MCOMPILER-10] - display summary information including number of
compiler errors when compiler plugin fails.
* [MCOMPILER-52] - Need a way to specify the debug level
* [MCOMPILER-53] - org.apache.maven.BuildFailureException :
Compilation failure. The system is out of resources.
* [MCOMPILER-59] - Compilation fails on warning messages from javac
(Java
6)
* [MCOMPILER-74] - build failure when executable path contains spaces
** Improvement
* [MCOMPILER-57] - State default source (1.3) and target (1.1) in
the documentation
* [MCOMPILER-70] - use ${project.build.sourceEncoding} as default
value for encoding parameter
* [MCOMPILER-73] - Warn about usage of platform encoding
* [MCOMPILER-111] - Allow to configure fork mode via system property
** New Feature
* [MCOMPILER-83] - add separate configuration for test compiler
** Task
* [MCOMPILER-112] - Change mavenVersion from 2.0.6 to 2.0.9 in the prereq
Enjoy,
-The Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re : [ANN] Maven Compiler Plugin 2.1 Released
Hi,
Is this version toolchains aware? This is not written in release notes and the
page about toolchains [1] was not updated.
Regards,
Julien
[1] http://maven.apache.org/guides/mini/guide-using-toolchains.html
De : Stephen Connolly steph...@apache.org
À : annou...@maven.apache.org; Maven Users List users@maven.apache.org
Cc : Maven Developers List d...@maven.apache.org
Envoyé le : Sam 2 Janvier 2010, 13 h 35 min 41 s
Objet : [ANN] Maven Compiler Plugin 2.1 Released
The Maven team is pleased to announce the release of the Maven
Compiler Plugin, version 2.1
This plugin is used to compile the sources of your project. .
http://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.1/version
/plugin
Release Notes - Maven 2.x Compiler Plugin - Version 2.1
** Bug
* [MCOMPILER-10] - display summary information including number of
compiler errors when compiler plugin fails.
* [MCOMPILER-52] - Need a way to specify the debug level
* [MCOMPILER-53] - org.apache.maven.BuildFailureException :
Compilation failure. The system is out of resources.
* [MCOMPILER-59] - Compilation fails on warning messages from javac (Java 6)
* [MCOMPILER-74] - build failure when executable path contains spaces
** Improvement
* [MCOMPILER-57] - State default source (1.3) and target (1.1) in
the documentation
* [MCOMPILER-70] - use ${project.build.sourceEncoding} as default
value for encoding parameter
* [MCOMPILER-73] - Warn about usage of platform encoding
* [MCOMPILER-111] - Allow to configure fork mode via system property
** New Feature
* [MCOMPILER-83] - add separate configuration for test compiler
** Task
* [MCOMPILER-112] - Change mavenVersion from 2.0.6 to 2.0.9 in the prereq
Enjoy,
-The Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re : WTP support and Standard Directory Layout
If your configuration files need to be in the build path, I suggest to move them to src/main/resources. src/main/config is never used AFAIK, so it main be simply a conventional place to put config files that will not be packaged in the artifact (someone can correct me if I am wrong). ++ Julien - Message d'origine De : Richard Hauswald richard.hausw...@googlemail.com À : users@maven.apache.org Envoyé le : Mer 18 Novembre 2009, 13 h 09 min 35 s Objet : WTP support and Standard Directory Layout Hello list, as described in the Standard Directory Layout (http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html) configuration files should be placed under src/main/config . But this directory is not included in the build path. The directories src/main/filters src/test/java src/test/resources src/test/filters are ignored too. Is this intended behaviour or a bug? Thanks, Richard -- Richard Hauswald Blog: http://tnfstacc.blogspot.com/ LinkedIn: http://www.linkedin.com/in/richardhauswald Xing: http://www.xing.com/profile/Richard_Hauswald - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Updating properties defined in pom from command line
Hi,
I'm working on a script that will automatically release many artifacts. For
example I have 2 Maven projects (say A and B). B have a dependency on A. The
dependency version is expressed using a property (say ${A.version}).
In the SVN trunk, in B.pom, A.version=1-SNAPSHOT.
A and B are independent Maven modules (not multi-module).
Basically, the script is aware of the release order and will:
- svn checkout A
- mvn release:prepare release:perform -B -DreleaseVersion=1-RC1 (batch mode
so release version was a parameter of the script)
- svn checkout B
- update A dependency in B.pom to 1-RC1
- mvn release:prepare release:perform -B -DreleaseVersion=4-RC1
My question is: how can I update A dependency in B.pom? I tried to use
versions-maven-plugin but the plugin is too smart for my usage as it always try
to update to the latest released version. What I want is to be able to say:
update property named A.version to value 1-RC1 even if A was already released
in version 2.
Do you know a way to do this?
Thanks,
Julien
Re : Updating properties defined in pom from command line
Hi Stephen,
Have you already tested the solution you propose? I tried and it is not working
so I was wondering if there is something wrong in my use or if it is a plugin
bug.
My test case:
I have a property in my pom:
test.prop.version1.3/test.prop.version
running mvn versions:update-properties the value is changed to
test.prop.version1.4/test.prop.version
but when I put this configuration in the pom:
properties
...
property
nametest.prop.version/name
...
version[1.4]/version!--Testing with a fixed value--
...
/property
...
/properties
reverting to
test.prop.version1.3/test.prop.version
and running mvn versions:update-properties the value is not changed. There is
no error but only:
Property ${test.prop.version}: Leaving unchanged as 1.3
Of course using a property instead of a fixed value in property configuration
doesn't work better.
Any idea?
Thanks
Julien
De : Stephen Connolly stephen.alan.conno...@gmail.com
À : Maven Users List users@maven.apache.org
Envoyé le : Jeu 22 Octobre 2009, 12 h 15 min 57 s
Objet : Re: Updating properties defined in pom from command line
you should be able to define a range to restrict updates to within a
range...
e.g. add a config section with a version restriction specified and have that
defined by a property
project
...
build
...
plugins
...
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdversions-maven-plugin/artifactId
version1.0/version
configuration
...
properties
...
property
namemanchu.version/name
...
version[${magic}]/version
...
/property
...
/properties
...
/configuration
/plugin
...
/plugins
...
/build
...
/project
then
mvn versions:updateProperties -Dmagic=newAVersion
2009/10/22 Julien HENRY henr...@yahoo.fr
Hi,
I'm working on a script that will automatically release many artifacts. For
example I have 2 Maven projects (say A and B). B have a dependency on A. The
dependency version is expressed using a property (say ${A.version}).
In the SVN trunk, in B.pom, A.version=1-SNAPSHOT.
A and B are independent Maven modules (not multi-module).
Basically, the script is aware of the release order and will:
- svn checkout A
- mvn release:prepare release:perform -B -DreleaseVersion=1-RC1 (batch
mode so release version was a parameter of the script)
- svn checkout B
- update A dependency in B.pom to 1-RC1
- mvn release:prepare release:perform -B -DreleaseVersion=4-RC1
My question is: how can I update A dependency in B.pom? I tried to use
versions-maven-plugin but the plugin is too smart for my usage as it always
try to update to the latest released version. What I want is to be able to
say: update property named A.version to value 1-RC1 even if A was already
released in version 2.
Do you know a way to do this?
Thanks,
Julien
Re : Re : Updating properties defined in pom from command line
Bug submitted with 2 IT test cases (1st with value fixed in the pom and 2nd
with a property specified on the command line).
MVERSIONS-80
I didn't have looked at the plugin code yet and I would like to know if this is
something that will be easily fixed. What is your opinion?
Thanks,
Julien
- Message d'origine
De : Stephen Connolly stephen.alan.conno...@gmail.com
À : Maven Users List users@maven.apache.org
Envoyé le : Jeu 22 Octobre 2009, 13 h 36 min 30 s
Objet : Re: Re : Updating properties defined in pom from command line
sounds like a bug... if you can produce an integration test and file a JIRA
that would be great... I cannot look into this at the moment [swamped at
work]
2009/10/22 Julien HENRY
Hi Stephen,
Have you already tested the solution you propose? I tried and it is not
working so I was wondering if there is something wrong in my use or if it is
a plugin bug.
My test case:
I have a property in my pom:
1.3
running mvn versions:update-properties the value is changed to
1.4
but when I put this configuration in the pom:
...
test.prop.version
...
[1.4]
...
...
reverting to
1.3
and running mvn versions:update-properties the value is not changed. There
is no error but only:
Property ${test.prop.version}: Leaving unchanged as 1.3
Of course using a property instead of a fixed value in property
configuration doesn't work better.
Any idea?
Thanks
Julien
De : Stephen Connolly
À : Maven Users List
Envoyé le : Jeu 22 Octobre 2009, 12 h 15 min 57 s
Objet : Re: Updating properties defined in pom from command line
you should be able to define a range to restrict updates to within a
range...
e.g. add a config section with a version restriction specified and have
that
defined by a property
...
...
...
org.codehaus.mojo
versions-maven-plugin
1.0
...
...
manchu.version
...
[${magic}]
...
...
...
...
...
...
then
mvn versions:updateProperties -Dmagic=newAVersion
2009/10/22 Julien HENRY
Hi,
I'm working on a script that will automatically release many artifacts.
For
example I have 2 Maven projects (say A and B). B have a dependency on A.
The
dependency version is expressed using a property (say ${A.version}).
In the SVN trunk, in B.pom, A.version=1-SNAPSHOT.
A and B are independent Maven modules (not multi-module).
Basically, the script is aware of the release order and will:
- svn checkout A
- mvn release:prepare release:perform -B -DreleaseVersion=1-RC1 (batch
mode so release version was a parameter of the script)
- svn checkout B
- update A dependency in B.pom to 1-RC1
- mvn release:prepare release:perform -B -DreleaseVersion=4-RC1
My question is: how can I update A dependency in B.pom? I tried to use
versions-maven-plugin but the plugin is too smart for my usage as it
always
try to update to the latest released version. What I want is to be able
to
say: update property named A.version to value 1-RC1 even if A was
already
released in version 2.
Do you know a way to do this?
Thanks,
Julien
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Unit tests instrumented by cobertura are (very) slow
Hi, I have a project with a few CPU intensive tests (mainly computing algorithms). Running mvn clean test takes about 1min30 Running mvn clean cobertura:cobertura takes about 25min!!! Running mvn clean emma:emma takes about 2min Does anybody know what can be the reason why JUnit tests are taking so much time with cobertura? Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_15 Default locale: fr_FR, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows cobertura plugin: 2.3 emma plugin: 1.0-alpha-2 Thanks, Julien - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Maven Central Repository - Cleanup Efforts
- Message d'origine De : Albert Kurucz albert.kur...@gmail.com À : Maven Users List users@maven.apache.org Envoyé le : Lundi, 28 Septembre 2009, 19h39mn 00s Objet : Re: Maven Central Repository - Cleanup Efforts Tamas, could explain MRMs + grouping + mirrorOf or send a link? http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html 2009/9/28 Tamás Cservenák : Sorry for thread hijack, but was not able to resist... Another thing to think about, since it's adoption: On Mon, Sep 28, 2009 at 5:34 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: We do not allow definitions in pom files for a good reason. This seemed as a good idea, but think about it. Why would you _not_ put reposes in POMs? Because they will be _burned_ in to your POMs forever and your URLs may change down the road? Why is this better: * having repository defs in POMs, thus providing at least some usable info that a developer may use as starting point and google it up/search/look for it (where it went, what it was, etc) then: * providing _no_ useful information in POMs for future generations? Having no trace in your _build_ about needed reposes... Ah yes, _both_ cases are easily handled by MRMs + grouping + mirrorOf, but in 2nd case, the one building may only shoot in the dark, you did not provide _any_ information from what did you build your stuff. Think about it. ~t~ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
OSGi compatible dependencies
Hi, Foreword: I hadly know anything about OSGi. I recently discovered that Springsource is maintaining a parallel set of common dependencies in their own repository using modified artifactId. For example: dependency groupIdorg.junit/groupId artifactIdcom.springsource.org.junit/artifactId version4.5.0/version scopetest/scope /dependency As I said I'm not using OSGi but I was testing the Roo tool. To make it short Roo generate a Maven2 application and the pom.xml was full of this kind of dependencies. It was very annoying to me because even if I had all these dependencies already in my local repository, I had to download them again. After asking the reason of duplicating artifacts, someone explained to me [1] that these artifact are slighly modified to be OSGi compliant (AFAIK it means adding some standard properties in the manifest, correct me if I am wrong). Again I'm not an OSGi aware developer, but I'm very concerned by avoiding duplicate artifacts. Duplicating artifact will lead to confusion for developpers, it will increase size of both local and managed repositories, Sometimes there are good reason to duplicate, but for me this is not a good reason because AFAIK an OSGi compliant JAR can work in a regular application. I'm not blaming Spring guys for what they did, as this was certainly the only quick way to have it working with full control. But IMHO it would be better to think of a standard way to provide OSGi compliant JARs, especially because I heard Maven 3 will address this area. Some proposal : 1) Make all future JAR uploaded to Central OSGi compliant (is it possible to automatically enhance the MANIFEST?) = simplest/transparent solution for end users 2) OSGi compliant JARs use a separate classifier (we can have the regular junit-XX.jar and junit-XX-osgi.jar) = this solution can be used for all existing artifacts that can't be modified on central. What do you think? Regards, Julien [1] http://forum.springsource.org/showthread.php?p=255777
animal-sniffer on central?
Hi, I'm following the guide: http://maven.apache.org/guides/mini/guide-building-jdk14-on-jdk15.html The issue is I can't find animal-sniffer on the central Maven repository. I think it would be easier for users to have it on central repo. Or at least update the guide to tell that the dependency is only available on java.net repository. Thanks, Julien
animal-sniffer and cobertura issues
Hi, I'm testing animal-sniffer with my build. All was fine until I tried to generate the site. First, it seems that animal-sniffer is executed a lot of times during site generation. And worst is it is failing on Cobertura instrumented classes : [INFO] Checking unresolved references to org.jvnet.animal-sniffer:java1.4:1.0 [ERROR] Undefined reference: net/sourceforge/cobertura/coveragedata/ProjectData.getGlobalProjectData()Lnet/sourceforge/cobertura/coveragedata/ProjectData; in D:\Projects\X\myproject\x-myproject-webapp\target\generated-classes\cobertura\com\xx\myproject\action\ActionListAction.class ... ...(1 error for each and every class of my software) ... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Signature errors found. Verify them and put @IgnoreJRERequirement on them. Do you have any solution? Thanks Julien
Re : Maven collect JAR files into one ZIP
Hi, No need for the dependency plugin. The assembly plugin alone will do the job: in pom.xml plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.2-beta-3/version configuration descriptors descriptorsrc/main/assembly/bundle.xml/descriptor /descriptors /configuration /plugin bundle.xml assembly idbundle/id formats formatzip/format /formats dependencySets dependencySet unpackfalse/unpack scoperuntime/scope useProjectArtifacttrue/useProjectArtifact /dependencySet /dependencySets /assembly Regards, Julien De : Krabi imr...@hot.ee À : users@maven.apache.org Envoyé le : Jeudi, 4 Juin 2009, 15h13mn 30s Objet : Re: Maven collect JAR files into one ZIP Thanks! This solution is good enough :) Nick Stolwijk-4 wrote: I think the combination of dependency:copy-dependencies [1] and the assembly plugin will do what you want. [1] http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Thu, Jun 4, 2009 at 7:59 AM, Krabi imr...@hot.ee wrote: Yes I know that. Jar-with-deps is taking out all class files from all dep. JAR files and put them into one single JAR file. I don't need that. Is nice to have one ZIP where JARs are collected together.As same way how WAR files are built with maven. Inside WAR are also dep. jar files located. As I understand there isn't such a plug-in for that? If I need develop it by my self, is it hard do develop? What libraries/APIs I must to know? Is there POM parser and some Maven APIs for getting for project(for POM) list of all JARs(recursively resolved) with full path from local repository(like C:\Repo\org\some\lib\1.0\x-1.0.jar)? I know basic of making plug-ins but I don't know much about Maven APIs - how to get list of files and how to get maven context info(repository location, etc) and how to get plug-in configuration? Does I need to parse POM and toher XML files by my self or that functionality is supported by some Maven API? Any suggestion to read, search? Wayne Fay wrote: I think that better is to have plug-in that resolves deps(from POM) and adds into one ZIP. Jar with deps is not nice solution - long build proccess and I cant send send ~50MB files. You realize that the Jar file format is essentially zip plus some text files, right? What do you think would be magically different in this proposed Zip vs what Jar with deps is producing? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Maven-collect-JAR-files-into-one-ZIP-tp23849432p23864206.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Maven-collect-JAR-files-into-one-ZIP-tp23849432p23869693.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : WebLogic Plugin Sourcecode
Hi, https://svn.codehaus.org/mojo/branches/weblogic-maven-plugin-2.8.0/ Regards, Julien De : Inman, Peter peterin...@mcpplc.com À : Maven Users List users@maven.apache.org Envoyé le : Mercredi, 3 Juin 2009, 10h57mn 24s Objet : WebLogic Plugin Sourcecode I'm trying to use the maven-weblogic-plugin version 2.8 as we're deploying on WebLogic 8.1. When I try and do a release:prepare, it fails as the 2.8 version I have is a SNAPSHOT version. Sounds an odd question, but does anyone know where the source code is located so I can build a release version locally? I've checked all the usual places, but can't seem to find it. Pete
Re : Determining real GAV for java.servlet:servlet-api
Correct me if I am wrong but I think servlet-api should be set to provided scope so it doesn't really matter if this is not exactly the same JAR as long as the interfaces are the same. Regards, Julien De : Anders Hammar and...@hammar.net À : Maven Users List users@maven.apache.org Envoyé le : Lundi, 25 Mai 2009, 8h28mn 17s Objet : Re: Determining real GAV for java.servlet:servlet-api Ok, so it the servlet api jar version for JBoss 4.2.2 you're looking for? I think that would be version 2.5-brew in JBoss terms (not 2.4 as I wrote in my last mail). It's outlined in JBoss' build script: http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_4_2_2_GA/build/build-thirdparty.xml You'll find it here: http://repository.jboss.org/sun-servlet/2.5-brew/ (Still not a maven repo.) Yes, it's mess with JBoss jars... /Anders On Mon, May 25, 2009 at 08:17, daniel.green october...@gmail.com wrote: Gah, I posted the wrong GAV data. The correct one has java-servlet as the artifact id. The given does in fact work for jsp-api, just not for java-servlet. Wayne Fay wrote: groupIdjavax.servlet/groupId artifactIdjsp-api/artifactId version2.0/version Any reason this won't work? groupIdjavax.servlet/groupId artifactIdjsp-api/artifactId version2.0/version Taken from: http://repo1.maven.org/maven2/javax/servlet/jsp-api/2.0/jsp-api-2.0.pom Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Determining-real-GAV-for-java.servlet%3Aservlet-api-tp23699126p23701698.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : M2 and Eclipse
Hi, Do you have declared servlet-api as a dependency in your pom? If yes, which version? Regards, Julien - Message d'origine De : Alexander Vaysberg w...@vaisberg.de À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 23 Avril 2009, 13h55mn 55s Objet : M2 and Eclipse Hi, i have a Problem with M2Plugin in Eclipse. If I generate the project with mvn eclipse:m2eclipse then the org.eclipse.wst.common.project.facet.core.xml has : faceted-project fixed facet=jst.java/ fixed facet=jst.web/ installed facet=jst.web version=2.4/ installed facet=jst.java version=5..0/ /faceted-project But, if I used the in Eclipse Update Project Configuration than I have: ?xml version=1.0 encoding=UTF-8? faceted-project fixed facet=jst.java/ fixed facet=jst.web/ installed facet=jst.java version=5.0/ installed facet=jst.web version=2.5/ /faceted-project The Problem ist jst.web version=2.5. I use Tomcat 5.5(Tomcat version 5.5 only supports J2EE 1.2, 1.3, and 1.4 Web modules). Tomcat 5.5 is 2.4. How can I it configuration, that is the same if I it Update Project Configuration. Alexander Vaysberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Re : M2 and Eclipse
Forgot my previous message. According to [1] it seems it is not based on servlet-api version but on compiler version. [1] : http://docs.codehaus.org/display/M2ECLIPSE/Maven+To+WTP Julien - Message d'origine De : Julien HENRY henr...@yahoo.fr À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 23 Avril 2009, 14h11mn 11s Objet : Re : M2 and Eclipse Hi, Do you have declared servlet-api as a dependency in your pom? If yes, which version? Regards, Julien - Message d'origine De : Alexander Vaysberg w...@vaisberg.de À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 23 Avril 2009, 13h55mn 55s Objet : M2 and Eclipse Hi, i have a Problem with M2Plugin in Eclipse. If I generate the project with mvn eclipse:m2eclipse then the org.eclipse.wst.common.project.facet.core.xml has : faceted-project fixed facet=jst.java/ fixed facet=jst.web/ installed facet=jst.web version=2.4/ installed facet=jst.java version=5..0/ /faceted-project But, if I used the in Eclipse Update Project Configuration than I have: ?xml version=1.0 encoding=UTF-8? faceted-project fixed facet=jst.java/ fixed facet=jst.web/ installed facet=jst..java version=5.0/ installed facet=jst.web version=2.5/ /faceted-project The Problem ist jst.web version=2.5. I use Tomcat 5.5(Tomcat version 5.5 only supports J2EE 1.2, 1.3, and 1.4 Web modules).. Tomcat 5.5 is 2.4. How can I it configuration, that is the same if I it Update Project Configuration. Alexander Vaysberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Re : Re : M2 and Eclipse
It seems that if in maven-compiler-plugin configuration you have source1.5/source target1.5/target then the web version will be 2.5. See the mapping file here: http://svn.sonatype.org/m2eclipse/branches/raghu/org.maven.ide.eclipse.wtp.facet/src/org/maven/ide/eclipse/wtp/facet/jst.web.properties Regards - Message d'origine De : Alexander Vaysberg w...@vaisberg.de À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 23 Avril 2009, 15h10mn 19s Objet : Re: Re : Re : M2 and Eclipse ok, and how I can it's management? Julien HENRY schrieb: Forgot my previous message. According to [1] it seems it is not based on servlet-api version but on compiler version. [1] : http://docs.codehaus.org/display/M2ECLIPSE/Maven+To+WTP Julien - Message d'origine De : Julien HENRY henr...@yahoo.fr À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 23 Avril 2009, 14h11mn 11s Objet : Re : M2 and Eclipse Hi, Do you have declared servlet-api as a dependency in your pom? If yes, which version? Regards, Julien - Message d'origine De : Alexander Vaysberg w...@vaisberg.de À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 23 Avril 2009, 13h55mn 55s Objet : M2 and Eclipse Hi, i have a Problem with M2Plugin in Eclipse. If I generate the project with mvn eclipse:m2eclipse then the org.eclipse.wst.common.project.facet.core.xml has : faceted-project fixed facet=jst.java/ fixed facet=jst.web/ installed facet=jst.web version=2.4/ installed facet=jst.java version=5..0/ /faceted-project But, if I used the in Eclipse Update Project Configuration than I have: ?xml version=1.0 encoding=UTF-8? faceted-project fixed facet=jst.java/ fixed facet=jst.web/ installed facet=jst..java version=5.0/ installed facet=jst.web version=2.5/ /faceted-project The Problem ist jst.web version=2.5. I use Tomcat 5.5(Tomcat version 5.5 only supports J2EE 1..2, 1.3, and 1.4 Web modules).. Tomcat 5.5 is 2.4. How can I it configuration, that is the same if I it Update Project Configuration. Alexander Vaysberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache..org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Re : Re : Re : M2 and Eclipse
Good point. According to me, m2eclipse should rely on servlet API version instead of Java version. Perhaps should you open a bug on m2eclipse tracker: https://issues.sonatype.org/browse/MNGECLIPSE Regards, Julien - Message d'origine De : Alexander Vaysberg w...@vaisberg.de À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 23 Avril 2009, 15h30mn 44s Objet : Re: Re : Re : Re : M2 and Eclipse but, if i have a project with 1.5 jdk and must using the 2.4 web server? Julien HENRY schrieb: It seems that if in maven-compiler-plugin configuration you have source1.5/source target1.5/target then the web version will be 2.5. See the mapping file here: http://svn.sonatype.org/m2eclipse/branches/raghu/org.maven.ide.eclipse.wtp.facet/src/org/maven/ide/eclipse/wtp/facet/jst.web.properties Regards - Message d'origine De : Alexander Vaysberg w...@vaisberg.de À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 23 Avril 2009, 15h10mn 19s Objet : Re: Re : Re : M2 and Eclipse ok, and how I can it's management? Julien HENRY schrieb: Forgot my previous message. According to [1] it seems it is not based on servlet-api version but on compiler version. [1] : http://docs.codehaus.org/display/M2ECLIPSE/Maven+To+WTP Julien - Message d'origine De : Julien HENRY henr...@yahoo.fr À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 23 Avril 2009, 14h11mn 11s Objet : Re : M2 and Eclipse Hi, Do you have declared servlet-api as a dependency in your pom? If yes, which version? Regards, Julien - Message d'origine De : Alexander Vaysberg w...@vaisberg.de À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 23 Avril 2009, 13h55mn 55s Objet : M2 and Eclipse Hi, i have a Problem with M2Plugin in Eclipse. If I generate the project with mvn eclipse:m2eclipse then the org.eclipse.wst.common.project.facet.core.xml has : faceted-project fixed facet=jst.java/ fixed facet=jst.web/ installed facet=jst.web version=2.4/ installed facet=jst.java version=5..0/ /faceted-project But, if I used the in Eclipse Update Project Configuration than I have: ?xml version=1.0 encoding=UTF-8? faceted-project fixed facet=jst.java/ fixed facet=jst.web/ installed facet=jst..java version=5.0/ installed facet=jst.web version=2.5/ /faceted-project The Problem ist jst.web version=2.5. I use Tomcat 5.5(Tomcat version 5.5 only supports J2EE 1..2, 1.3, and 1.4 Web modules).. Tomcat 5.5 is 2.4. How can I it configuration, that is the same if I it Update Project Configuration. Alexander Vaysberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache..org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven..apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven..apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Build RCP application with Maven
Hi, Thanks for the pointer, I will look at Tycho. What about Maven PDE plugin (http://mojo.codehaus.org/pde-maven-plugin/)? Is this plugin in a stable state? Thanks, Julien - Message d'origine De : Konstantin Domoratskyy kost...@cs.tu-berlin.de À : Maven Users List users@maven.apache.org Envoyé le : Vendredi, 13 Février 2009, 23h44mn 58s Objet : Re: Build RCP application with Maven Hi, it works with Tycho. But Tycho configuration isn't trivial. E.g. all dependencies should be declared in MANIFEST-file not in pom. See more in http://docs.codehaus.org/display/M2ECLIPSE/Tycho+project+overview Best regards, Konstantin --- Hi all, I would like to know if someone already build an Eclipse RCP application with Maven. Thanks for your feedbacks. Julien __ Ne pleurez pas si votre Webmail ferme ! Récupérez votre historique sur Yahoo! Mail ! http://fr.docs..yahoo.com/mail/transfert_mails.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org __ Ne pleurez pas si votre Webmail ferme ! Récupérez votre historique sur Yahoo! Mail ! http://fr.docs.yahoo.com/mail/transfert_mails.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Build RCP application with Maven
Hi all, I would like to know if someone already build an Eclipse RCP application with Maven. Thanks for your feedbacks. Julien __ Ne pleurez pas si votre Webmail ferme ! Récupérez votre historique sur Yahoo! Mail ! http://fr.docs.yahoo.com/mail/transfert_mails.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Maven 2 / Web-Services (Axis2)
Hi, You may try to create your own plugin or cargo extension to deploy aar to axis2 server. Alternatly you can use a fake web application to package your service as a WAR. It is no more an aar but perhaps it may help: http://wso2.org/library/90 Regards, Julien - Message d'origine De : Karl Heinz Marbaise [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Lundi, 16 Juin 2008, 14h22mn 15s Objet : Re: Maven 2 / Web-Services (Axis2) Hi, after taken some deep looks into different areas I have found a way which is 80% working... I've found the cargo framework which is capeable to install, start and deploy file to it...and in relationship with Maven 2 as well.. http://cargo.codehaus.org/Deploying+to+a+running+container But currently i'm struggling with the Axis2 service archive which will not be deployed to the Tomcat (in this case) and i have found no way to deploy to the stand-alone server of Axis2 May be i find a way Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr
Please release wagon-ftp
Hi, Could you please release a new version of wagon-ftp. I really need WAGONFTP-7 for deploying site. Thanks Julien _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re : Maven users in the industry
Hi, Here at Capgemini France, we are using Maven 2 + Continuum for a while. I don't know exactly the amount of people using it in the group, but I think most of the new J2EE projects use Maven. ++ Julien - Message d'origine De : Gilles Scokart [EMAIL PROTECTED] À : users@maven.apache.org Envoyé le : Mercredi, 11 Avril 2007, 10h00mn 55s Objet : Maven users in the industry Hi, Next week I have to make a presentation to my collegues. I will try to 'sell' maven, and I would like to say something like Look, Maven is now very used in the industry, It's for instance used by Did you know any companies using Maven, more particularily in Belgium and Europe, but worlwide would be ok also? Thanks for your help. Gilles -- View this message in context: http://www.nabble.com/Maven-users-in-the-industry-tf3557876s177.html#a9934912 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re : Using alternative JDK
AND if for some other obscure reason use w2k OR have very many source files, the forked compiler command line will blow up and fail. Should be fixed with latest compiler-plugin. FYI : http://jira.codehaus.org/browse/MCOMPILER-22 ++ Julien ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
War plugin dependencies resolution bug
Hi, I'm using maven-war-plugin-2.0-beta-2, and I don't understand the dependency resolution mechanism: Here is the first example: project modelVersion4.0.0/modelVersion groupIdfoo/groupId artifactIdbar/artifactId version1.0-SNAPSHOT/version packagingwar/packaging dependencies dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.12/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.13/version /dependency /dependencies /project Running mvn clean package, I get target/bar-1.0-SNAPSHOT.war, with the following content: WEB-INF/lib/log4j-1.2.12.jar WEB-INF/lib/log4j-1.2.13.jar Second example: project modelVersion4.0.0/modelVersion groupIdfoo/groupId artifactIdbar/artifactId version1.0-SNAPSHOT/version packagingwar/packaging dependencies dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.13/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.12/version /dependency /dependencies /project Running mvn clean package, I get target/bar-1.0-SNAPSHOT.war, with the following content: WEB-INF/lib/log4j-1.2.13.jar Perhaps the first case is a wanted feature, but for me it's a bug. If already reported on Jira, could you please give me the link. Thanks Julien ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Re : War plugin dependencies resolution bug
Another try with maven-war-plugin-2.0.2 and a pom more similar to my real problem: project modelVersion4.0.0/modelVersion groupIdfoo/groupId artifactIdbar/artifactId version1.0-SNAPSHOT/version packagingwar/packaging dependencies dependency groupIdavalon/groupId artifactIdavalon-framework/artifactId version4.1.4/version /dependency dependency groupIdfop/groupId artifactIdfop/artifactId version0.20.5/version /dependency /dependencies build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.2/version /plugin /plugins /pluginManagement /build /project First question : why 2.0.2 HAVE TO be specified (if not, 2.0-beta-2 is used) ? Second question: I have 2 avalon jar in my dependencies: WEB-INF/lib/avalon-framework-4.0.jar WEB-INF/lib/avalon-framework-4.1.4.jar How can I do to have only avalon-framework-4.1.4.jar ? Changing dependencies order does nothing this time. The only solution I found was to exclude avalon-framework dependency from fop, but I think Maven should do it by itself, right ? Thanks Julien - Message d'origine De : Julien HENRY [EMAIL PROTECTED] À : users@maven.apache.org Envoyé le : Lundi, 29 Janvier 2007, 11h28mn 36s Objet : War plugin dependencies resolution bug Hi, I'm using maven-war-plugin-2.0-beta-2, and I don't understand the dependency resolution mechanism: Here is the first example: project modelVersion4.0.0/modelVersion groupIdfoo/groupId artifactIdbar/artifactId version1.0-SNAPSHOT/version packagingwar/packaging dependencies dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.12/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.13/version /dependency /dependencies /project Running mvn clean package, I get target/bar-1.0-SNAPSHOT.war, with the following content: WEB-INF/lib/log4j-1.2.12.jar WEB-INF/lib/log4j-1.2.13.jar Second example: project modelVersion4.0.0/modelVersion groupIdfoo/groupId artifactIdbar/artifactId version1.0-SNAPSHOT/version packagingwar/packaging dependencies dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.13/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.12/version /dependency /dependencies /project Running mvn clean package, I get target/bar-1.0-SNAPSHOT.war, with the following content: WEB-INF/lib/log4j-1.2.13.jar Perhaps the first case is a wanted feature, but for me it's a bug. If already reported on Jira, could you please give me the link. Thanks Julien ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Re : Maven2 and Spring
Hi, The command you used generate a simple project. You should use another archetype for Spring. AFAIK there is no Spring archetype in the maven repository, but you can use the one provided by Webtide: http://www.webtide.com/resources.jsp I don't know if Webtide archetypes are available on a repository, but they suggest to download and install manually their archetypes. ++ Julien - Message d'origine De : Khabot, Zakaria [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Mardi, 23 Janvier 2007, 15h35mn 41s Objet : Maven2 and Spring Hi all, I have created a project using the command: mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes -DgroupId=fr.tge.test -DartifactId=Test Witch goal should I execute to generate a web app implementing the framework Spring and how to download the plugin. Thanks. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re : Assembly and multi-module project
I tried with mvn package assembly:assembly and I got exactly the same behavior. I also tried to build Maven 2.1 from SVN, and both mvn assembly:assembly and mvn package assembly:assembly failed with the same message. - Message d'origine De : Wendy Smoak [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Mercredi, 29 Novembre 2006, 1h21mn 50s Objet : Re: Assembly and multi-module project On 11/28/06, Julien HENRY [EMAIL PROTECTED] wrote: I think my xml file is well configured, but when I run mvn assembly:assembly, the plugin complains: [INFO] Failed to create assembly: Artifact: [moduleC] (included by module) does not have an artifact with a file. Please ensure the package phase is run before the assembly is generated. The documentation on the site claims that package phase is automatically run by assembly goal, so it should work. Any Idea ? On http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html under moduleSet, it says, NOTE: When using moduleSets from the command-line, it is required to pass first the package phase by doing: mvn package assembly:assembly. This bug/issue is scheduled to be addressed by Maven 2.1. However, the docs were published on Nov 7th, so there may be some documentation there on as-yet-unreleased features. More examples of multi-module assemblies would be great. I'm currently having trouble getting assembly to do what I want. :( -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Re : Re : Maven and Sourceforge (Change report and issue tracking)
Finally, I found a much better way to generate issue URL (wich will work with bugs, patchs, feature requests and support requests). I will update the wiki directly. ++ Julien - Message d'origine De : Wim Deblauwe [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Mercredi, 29 Novembre 2006, 9h00mn 46s Objet : Re: Re : Maven and Sourceforge (Change report and issue tracking) Thank you! I've updated the wiki with your information, I'm sure this will help a lot of people. regards, Wim 2006/11/28, Julien HENRY [EMAIL PROTECTED]: Here is how I configure changes report and issue tracking section with sourceforge: In the pom.xml: issueManagement systemsourceforge/system!--don't care-- url http://sourceforge.net/tracker/?atid=497982amp;group_id=61302 /url /issueManagement (Note the amp; instead of ) plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changes-plugin/artifactId inheritedfalse/inherited reportSets reportSet reports reportchanges-report/report /reports /reportSet /reportSets configuration issueLinkTemplate %URL%/index.php?func=detailamp;aid=%ISSUE%amp;group_id=61302amp;atid=497982 /issueLinkTemplate /configuration /plugin You need to customize atid, group_id, aid for your project. group_id refers to your project atid refers to the section (bugs, feature request or patch) aid refers to the issue number Now in your change.xml, you can put: action type=fix dev=Julien Henry due-to=Pete Bull issue=1554148 bla bla /action This will generate a link for your issue like this: %URL% = http://sourceforge.net/tracker/?atid=497982amp;group_id=61302 %ISSUE% = 1554148 The only problem I have with this configuration is I can't add a link for feature requests or patches (only bugs) Hope it helps. ++ Julien - Message d'origine De : Wim Deblauwe [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Mardi, 28 Novembre 2006, 16h18mn 23s Objet : Re: Maven and Sourceforge Thanks for the input, I've updated the wiki page with it. This is unix notation for file permissions: r = 4 (read permission) w = 2 (write permission) x = 1 (execute permission) The first number is for user The second number is for group The third is for what's left ;-) So 7 = 4 + 2 + 1 = rwx 5 = 4 + 1 = r-x 775: means owning user can do anything, all users of the owning group can do anything, anybody else can read and execute. For more infos on unix file permissions : http://www.freeos.com/articles/3127/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Assembly and multi-module project
Hi,
I have a multi-module project:
pom.xml
\_moduleA
\_moduleB
\_moduleC
I want to create a release package with the following content:
--
moduleA.jar
moduleC.jar
lib/moduleAdependency1.jar
...
lib/moduleAdependencyN.jar
lib/moduleCdependency1.jar
...
lib/moduleCdependencyN.jar
src/moduleA-sources.jar
src/moduleC-sources.jar
javadoc/moduleA-javadoc.jar
javadoc/moduleC-javadoc.jar
--
I think my xml file is well configured, but when I run mvn assembly:assembly,
the plugin complains:
[INFO] Failed to create assembly: Artifact: [moduleC] (included by module) does
not have an artifact with a file. Please ensure the package phase is run before
the assembly is generated.
The documentation on the site claims that package phase is automatically run by
assembly goal, so it should work. Any Idea ?
Thanks
Julien
--
Real message:
[INFO] [jar:jar]
[INFO] Building jar:
D:\jhenry\jwebunit-1.x\jwebunit-htmlunit-plugin\target\jwebunit-htmlunit-plugin-1.4-SNAPSHOT.jar
[INFO] [assembly:assembly {execution: release}]
[INFO] Reading assembly descriptor:
D:\jhenry\jwebunit-1.x\src\assemble\release.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to create assembly: Artifact:
net.sourceforge.jwebunit:jwebunit-htmlunit-plugin:jar:1.4-SNAPSHOT (included by
module) does not have an a
rtifact with a file. Please ensure the package phase is run before the assembly
is generated.
---
release.xml:
assembly
idrelease/id
formats
formatzip/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
fileSets
fileSet
includes
includeREADME*/include
includeLICENSE*/include
/includes
/fileSet
fileSet
directoryjwebunit-core/target//directory
outputDirectoryjavadoc/outputDirectory
includes
include*-javadoc.jar/include
/includes
/fileSet
fileSet
directoryjwebunit-htmlunit-plugin/target//directory
outputDirectoryjavadoc/outputDirectory
includes
include*-javadoc.jar/include
/includes
/fileSet
fileSet
directoryjwebunit-core/target//directory
outputDirectorysrc/outputDirectory
includes
include*-sources.jar/include
/includes
/fileSet
fileSet
directoryjwebunit-htmlunit-plugin/target//directory
outputDirectorysrc/outputDirectory
includes
include*-sources.jar/include
/includes
/fileSet
/fileSets
moduleSets
moduleSet
includes
includenet.sourceforge.jwebunit:jwebunit-htmlunit-plugin/include
includenet.sourceforge.jwebunit:jwebunit-core/include
/includes
binaries
includeDependenciestrue/includeDependencies
unpackfalse/unpack
dependencySets
dependencySet
scoperuntime/scope
outputDirectorylib/outputDirectory
/dependencySet
/dependencySets
/binaries
/moduleSet
/moduleSets
/assembly
___
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur
Yahoo! Questions/Réponses
http://fr.answers.yahoo.com
Re : Maven and Sourceforge (Change report and issue tracking)
Here is how I configure changes report and issue tracking section with sourceforge: In the pom.xml: issueManagement systemsourceforge/system!--don't care-- url http://sourceforge.net/tracker/?atid=497982amp;group_id=61302 /url /issueManagement (Note the amp; instead of ) plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changes-plugin/artifactId inheritedfalse/inherited reportSets reportSet reports reportchanges-report/report /reports /reportSet /reportSets configuration issueLinkTemplate %URL%/index.php?func=detailamp;aid=%ISSUE%amp;group_id=61302amp;atid=497982 /issueLinkTemplate /configuration /plugin You need to customize atid, group_id, aid for your project. group_id refers to your project atid refers to the section (bugs, feature request or patch) aid refers to the issue number Now in your change.xml, you can put: action type=fix dev=Julien Henry due-to=Pete Bull issue=1554148 bla bla /action This will generate a link for your issue like this: %URL% = http://sourceforge.net/tracker/?atid=497982amp;group_id=61302 %ISSUE% = 1554148 The only problem I have with this configuration is I can't add a link for feature requests or patches (only bugs) Hope it helps. ++ Julien - Message d'origine De : Wim Deblauwe [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Mardi, 28 Novembre 2006, 16h18mn 23s Objet : Re: Maven and Sourceforge Thanks for the input, I've updated the wiki page with it. This is unix notation for file permissions: r = 4 (read permission) w = 2 (write permission) x = 1 (execute permission) The first number is for user The second number is for group The third is for what's left ;-) So 7 = 4 + 2 + 1 = rwx 5 = 4 + 1 = r-x 775: means owning user can do anything, all users of the owning group can do anything, anybody else can read and execute. For more infos on unix file permissions : http://www.freeos.com/articles/3127/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Re : Maven and Sourceforge (mailing lists and subversion)
Here is how I configure my pom with Sourceforge mailing list and subversion (need to be updated for CVS) : mailingLists mailingList nameJWebUnit Development Mailing list/name subscribe http://lists.sourceforge.net/mailman/listinfo/jwebunit-development /subscribe unsubscribe http://lists.sourceforge.net/mailman/listinfo/jwebunit-development /unsubscribe archive http://sourceforge.net/mailarchive/forum.php?forum_id=40831 /archive postjwebunit-development@lists.sourceforge.net/post /mailingList mailingList nameJWebUnit User Mailing list/name subscribe http://lists.sourceforge.net/mailman/listinfo/jwebunit-users /subscribe unsubscribe http://lists.sourceforge.net/mailman/listinfo/jwebunit-users /unsubscribe archive http://sourceforge.net/mailarchive/forum.php?forum_id=40830 /archive postjwebunit-users@lists.sourceforge.net/post /mailingList /mailingLists scm connection scm:svn:https://svn.sourceforge.net/svnroot/jwebunit/trunk /connection developerConnection scm:svn:https://svn.sourceforge.net/svnroot/jwebunit/trunk /developerConnection url http://svn.sourceforge.net/viewcvs.cgi/jwebunit/trunk /url /scm Customize the bold part with your own project name and forum_id. I just forgot that you will also need to configure the report plugin: plugin groupIdorg.apache.maven.plugins/groupId artifactId maven-project-info-reports-plugin /artifactId reportSets reportSet reports reportindex/report reportdependencies/report reportproject-team/report reportmailing-list/report reportlicense/report reportissue-tracking/report reportscm/report reportsummary/report /reports /reportSet /reportSets /plugin ++ Julien - Message d'origine De : Wim Deblauwe [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Mardi, 28 Novembre 2006, 16h18mn 23s Objet : Re: Maven and Sourceforge Thanks for the input, I've updated the wiki page with it. This is unix notation for file permissions: r = 4 (read permission) w = 2 (write permission) x = 1 (execute permission) The first number is for user The second number is for group The third is for what's left ;-) So 7 = 4 + 2 + 1 = rwx 5 = 4 + 1 = r-x 775: means owning user can do anything, all users of the owning group can do anything, anybody else can read and execute. For more infos on unix file permissions : http://www.freeos.com/articles/3127/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Running both unit and integration tests in the same module
Hi, I would like to run both unit tests and integration tests in the same project. I don't want to create a separate module for integration tests (unlike Better Builds With Maven book). With only one project (and one pom), I want the following lifecycle: Phase |Action - compile | compile src/main/java ... test-compile| compile src/test/java test | run unit test that are in target/test-classes ... pre-integration-test | compile src/it/java in target/it-classes integration-test | run it tests that are in target/it-classes The problem I have is for compiling and running IT tests. The compiler plugin only have two goals (compiler:compile and compiler:testCompile). In BBWM book, the testCompile goal is customized to fit with src/it directory, but this configuration prevent running unit test, because we have to define testSourceDirectorysrc/it/testSourceDirectory. How can I run both unit tests and integration tests ? Thank you Julien ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Re : Running both unit and integration tests in the same module
OK, so I'll have to wait for Maven 2.1 ;) Thanks - Message d'origine De : Mark Hobson [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Lundi, 27 Novembre 2006, 10h33mn 07s Objet : Re: Running both unit and integration tests in the same module On 27/11/06, Julien HENRY [EMAIL PROTECTED] wrote: I would like to run both unit tests and integration tests in the same project. I don't want to create a separate module for integration tests (unlike Better Builds With Maven book). You can achieve this, but it's not too pretty. See: http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Re : Starting/Stopping Jetty for integration testing
Thank you very much for all this informations guys. ++ Julien - Message d'origine De : Wendy Smoak [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Vendredi, 24 Novembre 2006, 17h41mn 48s Objet : Re: Starting/Stopping Jetty for integration testing On 11/24/06, Julien HENRY [EMAIL PROTECTED] wrote: I want to execute jetty:run at the pre-integration-test phase and stop it (like Ctrl+C) at the post-integration-test phase. In addition to the plugin that has already been mentioned, Cargo also has a Java API that can be very useful for integration testing. Instead of binding plugin executions to lifecycle phases, you can start and stop containers from Java code, for example in JUnit TestSetup class. Here's an example: http://shale.apache.org/shale-test/apidocs/org/apache/shale/test/cargo/CargoTestSetup.html http://svn.apache.org/repos/asf/shale/framework/trunk/shale-test/src/main/java/org/apache/shale/test/cargo/CargoTestSetup.java -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Starting/Stopping Jetty for integration testing
Hi, I want to execute jetty:run at the pre-integration-test phase and stop it (like Ctrl+C) at the post-integration-test phase. The problem is jetty:run wait for being killed undefinitly and integration-test phase is never executed. I don't know exactly how to do this. It may need to develop a new plugin or modify the existing one? Forking a JVM ? I think I could use an ant run task, but it's not very Maven compliant. (http://ptrthomas.wordpress.com/2006/10/10/how-to-start-and-stop-jetty-from-ant/) Thanks Julien ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Maven eclipse plugin error
Hi, I get this error when I try to generate Eclipse configuration (mvn eclipse:eclipse) : [INFO] Preparing eclipse:eclipse [INFO] artifact org.codehaus.mojo:javacc-maven-plugin: checking for updates from Maven CodeHaus Snapshots [INFO] artifact org.codehaus.mojo:javacc-maven-plugin: checking for updates from Maven Snapshots [INFO] artifact org.codehaus.mojo:javacc-maven-plugin: checking for updates from central [INFO] snapshot org.codehaus.mojo:javacc-maven-plugin:2.2-SNAPSHOT: checking for updates from Maven CodeHaus Snapshots [INFO] snapshot org.codehaus.mojo:javacc-maven-plugin:2.2-SNAPSHOT: checking for updates from Maven Snapshots Downloading: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/test/maven-eclipse-plugin-test.pom [WARNING] Unable to get resource from repository Maven CodeHaus Snapshots (http://snapshots.maven.codehaus.org/maven2) Downloading: http://people.apache.org/maven-snapshot-repository//org/apache/maven/plugins/maven-eclipse-plugin/test/maven-eclipse-plugin-test.pom [WARNING] Unable to get resource from repository Maven Snapshots (http://people.apache.org/maven-snapshot-repository/) Downloading: http://illiade.sud.capgemini.fr:/repository/org/apache/maven/plugins/maven-eclipse-plugin/test/maven-eclipse-plugin-test.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) Downloading: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/test/maven-eclipse-plugin-test.pom [WARNING] Unable to get resource from repository codehaus-snapshot (http://snapshots.maven.codehaus.org/maven2) Downloading: http://illiade.sud.capgemini.fr:/repository/org/apache/maven/plugins/maven-eclipse-plugin/test/maven-eclipse-plugin-test.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-eclipse-plugin Version: test Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-eclipse-plugin:pom:test from the specified remote repositories: Maven Snapshots (http://people.apache.org/maven-snapshot-repository/), central (http://repo1.maven.org/maven2), Maven CodeHaus Snapshots (http://snapshots.maven.codehaus.org/maven2), codehaus-snapshot (http://snapshots.maven.codehaus.org/maven2) Thanks for any help. ++ Julien ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Error when generating Dependencies report (SNAPSHOT)
Hi, This morning, I try to generate my project site and it failed. Yesterday it works... Any idea? ++ Julien [INFO] Generate Dependencies report. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org/apache/maven/shared/jar/Jar [INFO] [INFO] Trace java.lang.NoClassDefFoundError: org/apache/maven/shared/jar/Jar at org.apache.maven.report.projectinfo.dependencies.Dependencies.init(Dependencies.java:74) at org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:126) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:67) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:239) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:115) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Re : Re : Re : Re : Generate source code with a JavaCC parser.
It's ok, I think I got it thanks to plugin dependency.
Just have to fix the problem with aggregated Javadoc...
FYI, the interesting part of my pom :
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasegenerate-sources/phase
configuration
tasks
!--
Do nothing as we only want to create a new
source folder.
--
/tasks
sourceRoot
${project.build.directory}/generated-sources/main/java
/sourceRoot
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
executions
execution
phasegenerate-sources/phase
goals
goaljava/goal
/goals
/execution
/executions
configuration
mainClassWebTestCaseGenerator/mainClass
arguments
argument${basedir}/src/main/java/argument!--Input--
argument${project.build.directory}/generated-sources/main/java/argument!--Output--
/arguments
includePluginDependenciestrue/includePluginDependencies
includeProjectDependenciesfalse/includeProjectDependencies
/configuration
dependencies
dependency
groupIdnet.sourceforge.jwebunit/groupId
artifactIdjwebunit-webtestcase-generator/artifactId
version1.4-SNAPSHOT/version
/dependency
/dependencies
/plugin
/plugins
/build
- Message d'origine
De : Julien HENRY [EMAIL PROTECTED]
À : Maven Users List users@maven.apache.org
Envoyé le : Mardi, 21 Novembre 2006, 13h38mn 40s
Objet : Re : Re : Re : Generate source code with a JavaCC parser.
Hi Chris,
I have another issues with this configuration (Exec plugin + Empty Ant Task)).
First, Javadoc is not generated for the generated class. It is when I call mvn
javadoc:javadoc, but not with mvn site. Perhaps because I'm using
aggregate=true.
Second issue is I add the module containing the JavaCC parser as a dependency
in order to the exec plugin to find it. But this module is not required at
runtime, and I don't want it in the Eclipse classpath or in the bundle. Can I
configure the parser module as a plugin dependency and not as a project
dependency?
Thanks.
Julien
- Message d'origine
De : Chris Hilton [EMAIL PROTECTED]
À : Maven Users List users@maven.apache.org
Envoyé le : Vendredi, 17 Novembre 2006, 17h13mn 45s
Objet : RE: Re : Re : Generate source code with a JavaCC parser.
It might be worthwhile to use the Antrun plugin for the short term with a
java task and the sourceRoot config element so that you don't have to mix
your generated source code with the regular source (bad CM). Or even using the
exec plugin and an empty task Antrun plugin with the new sourceRoot might
work. You might also consider adding a feature request to JIRA for the exec
plugin to include a way to add a source directory.
Chris
-Original Message-
From: Julien HENRY [mailto:[EMAIL PROTECTED]
Sent: Friday, 17 November, 2006 07:08
To: Maven Users List
Subject: Re : Re : Generate source code with a JavaCC parser.
Finally, it works with another module. I just have to use the
javacc plugin in the generate-sources phase of this new
module. In the module where I want to generate source, I use
the exec plugin to run the Parser.
The only problem is I have to generate the new source file in
src/main/java because I have no way to specify a second
source directory in the pom (for example target/generated-sources).
Thanks !
- Message d'origine
De : Julien HENRY [EMAIL PROTECTED]
À : Maven Users List users@maven.apache.org Envoyé le :
Vendredi, 17 Novembre 2006, 9h48mn 58s Objet : Re : Generate
source code with a JavaCC parser.
Thanks for the reply.
I'm currently have a multi-module layout. Could it be
possible to put the parser in a new module? The problem I see
is the Parser.jar should be installed in the local repository
before the generate-sources phase of the module that need it
to generate the .java file.
Actually, I'm looking for a way to build
Re : Re : Re : Generate source code with a JavaCC parser.
Hi Chris, I have another issues with this configuration (Exec plugin + Empty Ant Task)). First, Javadoc is not generated for the generated class. It is when I call mvn javadoc:javadoc, but not with mvn site. Perhaps because I'm using aggregate=true. Second issue is I add the module containing the JavaCC parser as a dependency in order to the exec plugin to find it. But this module is not required at runtime, and I don't want it in the Eclipse classpath or in the bundle. Can I configure the parser module as a plugin dependency and not as a project dependency? Thanks. Julien - Message d'origine De : Chris Hilton [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Vendredi, 17 Novembre 2006, 17h13mn 45s Objet : RE: Re : Re : Generate source code with a JavaCC parser. It might be worthwhile to use the Antrun plugin for the short term with a java task and the sourceRoot config element so that you don't have to mix your generated source code with the regular source (bad CM). Or even using the exec plugin and an empty task Antrun plugin with the new sourceRoot might work. You might also consider adding a feature request to JIRA for the exec plugin to include a way to add a source directory. Chris -Original Message- From: Julien HENRY [mailto:[EMAIL PROTECTED] Sent: Friday, 17 November, 2006 07:08 To: Maven Users List Subject: Re : Re : Generate source code with a JavaCC parser. Finally, it works with another module. I just have to use the javacc plugin in the generate-sources phase of this new module. In the module where I want to generate source, I use the exec plugin to run the Parser. The only problem is I have to generate the new source file in src/main/java because I have no way to specify a second source directory in the pom (for example target/generated-sources). Thanks ! - Message d'origine De : Julien HENRY [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Vendredi, 17 Novembre 2006, 9h48mn 58s Objet : Re : Generate source code with a JavaCC parser. Thanks for the reply. I'm currently have a multi-module layout. Could it be possible to put the parser in a new module? The problem I see is the Parser.jar should be installed in the local repository before the generate-sources phase of the module that need it to generate the .java file. Actually, I'm looking for a way to build the whole project with only one command (easier for continuum). With your solution, I need to build and install the parser first, then build my regular project. Thanks again. Julien - Message d'origine De : Chris Hilton [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 16 Novembre 2006, 18h36mn 05s Objet : RE: Generate source code with a JavaCC parser. To my eyes (and how I've done it before), this would be two projects. One project to create the Parser and jar it. Then the second project would use that jar as a dependency and execute the appropriate class during the generate-sources phase. Or you could get a little fancy and have the first project actually generate a Maven plugin with the Parser and then bind that plugin appropriately in the second project. Hope that helps. Chris -Original Message- From: Julien HENRY [mailto:[EMAIL PROTECTED] Sent: Thursday, 16 November, 2006 10:01 To: users@maven.apache.org Subject: Generate source code with a JavaCC parser. Hi all, I want to generate Java code for my project with JavaCC. Actually, it's not JavaCC that generate final source code, but JavaCC will generate a parser that will parse one of the file of my project and generate the expected file. To be clearer, I have a Java file named WebTester.java and I want to generate WebTestCase.java. I wrote a JavaCC file (parser.jj) that generate a Parser.java. Once compiled, Parser.class will take WebTester.java and output WebTestCase.java. How can I integrate this in my build? I know the maven-javacc-plugin, but it's not exactly what I want. Indeed, the plugin create Parser.java from parser.jj and add it to the Maven build directory, but it doesn't provide a way to run the parser before compile phase. I'm considering using ant to compile/run Parser.java before the compile phase, but it's ugly. Do you know a better way? Thanks Julien __ _ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
Re : Generate source code with a JavaCC parser.
Thanks for the reply. I'm currently have a multi-module layout. Could it be possible to put the parser in a new module? The problem I see is the Parser.jar should be installed in the local repository before the generate-sources phase of the module that need it to generate the .java file. Actually, I'm looking for a way to build the whole project with only one command (easier for continuum). With your solution, I need to build and install the parser first, then build my regular project. Thanks again. Julien - Message d'origine De : Chris Hilton [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 16 Novembre 2006, 18h36mn 05s Objet : RE: Generate source code with a JavaCC parser. To my eyes (and how I've done it before), this would be two projects. One project to create the Parser and jar it. Then the second project would use that jar as a dependency and execute the appropriate class during the generate-sources phase. Or you could get a little fancy and have the first project actually generate a Maven plugin with the Parser and then bind that plugin appropriately in the second project. Hope that helps. Chris -Original Message- From: Julien HENRY [mailto:[EMAIL PROTECTED] Sent: Thursday, 16 November, 2006 10:01 To: users@maven.apache.org Subject: Generate source code with a JavaCC parser. Hi all, I want to generate Java code for my project with JavaCC. Actually, it's not JavaCC that generate final source code, but JavaCC will generate a parser that will parse one of the file of my project and generate the expected file. To be clearer, I have a Java file named WebTester.java and I want to generate WebTestCase.java. I wrote a JavaCC file (parser.jj) that generate a Parser.java. Once compiled, Parser.class will take WebTester.java and output WebTestCase.java. How can I integrate this in my build? I know the maven-javacc-plugin, but it's not exactly what I want. Indeed, the plugin create Parser.java from parser.jj and add it to the Maven build directory, but it doesn't provide a way to run the parser before compile phase. I'm considering using ant to compile/run Parser.java before the compile phase, but it's ugly. Do you know a better way? Thanks Julien __ _ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Re : Re : Generate source code with a JavaCC parser.
Finally, it works with another module. I just have to use the javacc plugin in the generate-sources phase of this new module. In the module where I want to generate source, I use the exec plugin to run the Parser. The only problem is I have to generate the new source file in src/main/java because I have no way to specify a second source directory in the pom (for example target/generated-sources). Thanks ! - Message d'origine De : Julien HENRY [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Vendredi, 17 Novembre 2006, 9h48mn 58s Objet : Re : Generate source code with a JavaCC parser. Thanks for the reply. I'm currently have a multi-module layout. Could it be possible to put the parser in a new module? The problem I see is the Parser.jar should be installed in the local repository before the generate-sources phase of the module that need it to generate the .java file. Actually, I'm looking for a way to build the whole project with only one command (easier for continuum). With your solution, I need to build and install the parser first, then build my regular project. Thanks again. Julien - Message d'origine De : Chris Hilton [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 16 Novembre 2006, 18h36mn 05s Objet : RE: Generate source code with a JavaCC parser. To my eyes (and how I've done it before), this would be two projects. One project to create the Parser and jar it. Then the second project would use that jar as a dependency and execute the appropriate class during the generate-sources phase. Or you could get a little fancy and have the first project actually generate a Maven plugin with the Parser and then bind that plugin appropriately in the second project. Hope that helps. Chris -Original Message- From: Julien HENRY [mailto:[EMAIL PROTECTED] Sent: Thursday, 16 November, 2006 10:01 To: users@maven.apache.org Subject: Generate source code with a JavaCC parser. Hi all, I want to generate Java code for my project with JavaCC. Actually, it's not JavaCC that generate final source code, but JavaCC will generate a parser that will parse one of the file of my project and generate the expected file. To be clearer, I have a Java file named WebTester.java and I want to generate WebTestCase.java. I wrote a JavaCC file (parser.jj) that generate a Parser.java. Once compiled, Parser.class will take WebTester.java and output WebTestCase.java. How can I integrate this in my build? I know the maven-javacc-plugin, but it's not exactly what I want. Indeed, the plugin create Parser.java from parser.jj and add it to the Maven build directory, but it doesn't provide a way to run the parser before compile phase. I'm considering using ant to compile/run Parser.java before the compile phase, but it's ugly. Do you know a better way? Thanks Julien __ _ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Generate source code with a JavaCC parser.
Hi all, I want to generate Java code for my project with JavaCC. Actually, it's not JavaCC that generate final source code, but JavaCC will generate a parser that will parse one of the file of my project and generate the expected file. To be clearer, I have a Java file named WebTester.java and I want to generate WebTestCase.java. I wrote a JavaCC file (parser.jj) that generate a Parser.java. Once compiled, Parser.class will take WebTester.java and output WebTestCase.java. How can I integrate this in my build? I know the maven-javacc-plugin, but it's not exactly what I want. Indeed, the plugin create Parser.java from parser.jj and add it to the Maven build directory, but it doesn't provide a way to run the parser before compile phase. I'm considering using ant to compile/run Parser.java before the compile phase, but it's ugly. Do you know a better way? Thanks Julien ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Cannot start continuum
:\Program Files\Telelogic\CM Synergy 6/3\bin;C:\WINDOWS\Microsoft/NET\Framework\v2/0/50727;C: \Sun\jwsdp-1/6\jwsdp-shared\bin; jvm 5 | Exception in thread main wrapper | JVM process exited with a code of 1, setting the wrapper exit code to 1. wrapper | JVM exited while loading the application. wrapper | JVM was only running for 0 seconds leading to a failed restart count of 5. wrapper | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. wrapper | There may be a configuration problem: please check the logs. wrapper | -- Wrapper Stopped Appuyez sur une touche pour continuer... -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice **Join the Collaborative Business Experience ** _ This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: Cannot start continuum
OK, there were quotes in the %PATH%. It works now. Perhaps an entry in the FAQ could be helpfull. ++ Julien Julien Henry a écrit : Hi, I just download continuum, and I follow getting started instructions. But I get errors, and I don't understand why. Can you give me some help? Here is the output (DEBUG Mode) : D:\continuum-1.0.3-bin\continuum-1.0.3\bin\win32run.bat wrapper | -- Wrapper Started as Console wrapper | Using system timer. wrapperp | server listening on port 32000. wrapper | Launching a JVM... wrapper | command: C:\Program Files\Java\jdk1.5.0_06\bin\java -Dclassworlds.conf=../../conf/classworlds.conf -Djava.io.temp=../../temp -Dplexus.cor e=../../core -Dplexus.home=../.. -Dplexus.system.path=D:\oracle\product\10.2.0\client_1\bin;C:\Program Files\Java\jdk1.5.0_06\bin;D:\oracle\ora92\bin ;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ Fichiers communs\GTK\2.0\bin;C:\PROGRA~1\ULTRAE~1;C:\PROGRA~1\WINCVS~1.3\CVSNT;d:\build\bin;C:\Program Files\apache-ant-1.6.5\bin;D:\jhenry\maven-1. 0.2\bin;D:\jhenry\maven-2.0.4\bin;C:\Program Files\Subversion\bin;C:\Program Files\Microsoft SQL Server\90\Tools\bin\;C:\Program Files\Telelogic\CM Sy nergy 6.3\bin;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\Sun\jwsdp-1.6\jwsdp-shared\bin; -Xms3m -Xmx128m -Djava.library.path=../../bin/win32 -classpath ../../core/boot/wrapper.jar;../../core/boot/classworlds-1.1-alpha-2.jar -Dwrapper.key=xqGCMLUlfBHKLfzr -Dwrapper.port=32000 -Dwrapper.d ebug=TRUE -Dwrapper.use_system_time=TRUE -Dwrapper.version=3.1.2 -Dwrapper.native_library=wrapper -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp org.codehaus.classworlds.Launcher ../../conf/plexus.xml wrapper | JVM started (PID=2100) jvm 1 | java.lang.NoClassDefFoundError: Files\apache-ant-1/6/5\bin;D:\jhenry\maven-1/0/2\bin;D:\jhenry\maven-2/0/4\bin;C:\Program Files\Subversion\ bin;C:\Program Files\Microsoft SQL Server\90\Tools\bin\;C:\Program Files\Telelogic\CM Synergy 6/3\bin;C:\WINDOWS\Microsoft/NET\Framework\v2/0/50727;C: \Sun\jwsdp-1/6\jwsdp-shared\bin; jvm 1 | Exception in thread main wrapper | JVM process exited with a code of 1, setting the wrapper exit code to 1. wrapper | JVM exited while loading the application. wrapper | JVM was only running for 0 seconds leading to a failed restart count of 1. wrapper | Waiting 5 seconds before launching another JVM. wrapper | Launching a JVM... wrapper | command: C:\Program Files\Java\jdk1.5.0_06\bin\java -Dclassworlds.conf=../../conf/classworlds.conf -Djava.io.temp=../../temp -Dplexus.cor e=../../core -Dplexus.home=../.. -Dplexus.system.path=D:\oracle\product\10.2.0\client_1\bin;C:\Program Files\Java\jdk1.5.0_06\bin;D:\oracle\ora92\bin ;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ Fichiers communs\GTK\2.0\bin;C:\PROGRA~1\ULTRAE~1;C:\PROGRA~1\WINCVS~1.3\CVSNT;d:\build\bin;C:\Program Files\apache-ant-1.6.5\bin;D:\jhenry\maven-1. 0.2\bin;D:\jhenry\maven-2.0.4\bin;C:\Program Files\Subversion\bin;C:\Program Files\Microsoft SQL Server\90\Tools\bin\;C:\Program Files\Telelogic\CM Sy nergy 6.3\bin;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\Sun\jwsdp-1.6\jwsdp-shared\bin; -Xms3m -Xmx128m -Djava.library.path=../../bin/win32 -classpath ../../core/boot/wrapper.jar;../../core/boot/classworlds-1.1-alpha-2.jar -Dwrapper.key=_cqdSj9v_UDNEtZt -Dwrapper.port=32000 -Dwrapper.d ebug=TRUE -Dwrapper.use_system_time=TRUE -Dwrapper.version=3.1.2 -Dwrapper.native_library=wrapper -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=2 org.tanukisoftware.wrapper.WrapperSimpleApp org.codehaus.classworlds.Launcher ../../conf/plexus.xml wrapper | JVM started (PID=3228) jvm 2 | java.lang.NoClassDefFoundError: Files\apache-ant-1/6/5\bin;D:\jhenry\maven-1/0/2\bin;D:\jhenry\maven-2/0/4\bin;C:\Program Files\Subversion\ bin;C:\Program Files\Microsoft SQL Server\90\Tools\bin\;C:\Program Files\Telelogic\CM Synergy 6/3\bin;C:\WINDOWS\Microsoft/NET\Framework\v2/0/50727;C: \Sun\jwsdp-1/6\jwsdp-shared\bin; jvm 2 | Exception in thread main wrapper | JVM process exited with a code of 1, setting the wrapper exit code to 1. wrapper | JVM exited while loading the application. wrapper | JVM was only running for 0 seconds leading to a failed restart count of 2. wrapper | Waiting 5 seconds before launching another JVM. wrapper | Launching a JVM... wrapper | command: C:\Program Files\Java\jdk1.5.0_06\bin\java -Dclassworlds.conf=../../conf/classworlds.conf -Djava.io.temp=../../temp -Dplexus.cor e=../../core -Dplexus.home=../.. -Dplexus.system.path=D:\oracle\product\10.2.0\client_1\bin;C:\Program Files\Java\jdk1.5.0_06\bin;D:\oracle\ora92\bin ;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C
Re : Problem with conflicting classes in classpath
The problem is a bit more complexe as Selenium RC Server uses Jetty 5.x In fact I only need to automatically run Selenium Server when my application, and I need to run Jetty 6 server before my test cases. I'm using a JUnit TestSetup to run Jetty 6 only one time, and it works fine. If I run manually Selenium Server in another JVN, it works fine. But as soon as I try to put Selenium Server in my pom as a dependency, I get errors at runtime. In fact, I would like Maven download selenium server in order to always have correct version, but I don't really need it in the classpath, as I can run something like execute(java -jar $M2_HOME/repository/org/openqa/selenium/server/selenium-server-XX.jar); Do you know if it's possible ? - Message d'origine De : Lee Meador [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org; Julien HENRY [EMAIL PROTECTED] Envoyé le : Jeudi, 21 Septembre 2006, 7h17mn 30s Objet : Re: Problem with conflicting classes in classpath If Selenium RC Server will run with Jetty 6 you may be able to add an exclusion to your dependency on Selenium. Here is an example from a pom of mine: dependency groupIdjmock/groupId artifactIdjmock-cglib/artifactId version1.0.1/version scopetest/scope exclusions exclusion groupIdcglib/groupId artifactIdcglib-full/artifactId /exclusion /exclusions /dependency Now, this is test but the principle is the same. I need JMock (cglib) in my application but I don't want cglib-full so I exclude it. What I want is cglib-nodep BTW so I have to add that dependency in myself. Some other messages recently have noted that there are sometimes issues related to exclusions in Maven 2.0.4 for which fixes exist but are not released. -- Lee On 9/21/06, Julien HENRY [EMAIL PROTECTED] wrote: Hi, I have a conflict with 2 versions of Jetty. The first one is a dependency of Selenium RC Server (Jetty 5x), and I'm using Jetty 6 for my tests. As soon as I add the Selenium Server dependency in my pom, I get strange error. How can I solve this issue ? Thanks Julien -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com
Problem with conflicting classes in classpath
Hi, I have a conflict with 2 versions of Jetty. The first one is a dependency of Selenium RC Server (Jetty 5x), and I'm using Jetty 6 for my tests. As soon as I add the Selenium Server dependency in my pom, I get strange error. How can I solve this issue ? Thanks Julien
How to deal with modules
Hi, I'm working on a scm plugin for Synergy. I would like to put it on continuum in my company, but I get an error from continuum: Continuum Error * Cannot build maven project from /tmp/continuum/svn/laposte/maven-scm-provider-ccm/trunk/pom.xml (Cannot find parent: org.apache.maven.scm:maven-scm-providers for project: org.apache.maven.scm:maven-scm-provider-synergy:jar:1.0-SNAPSHOT). Check the logs for more details. Here is the pom : ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion parent artifactIdmaven-scm-providers/artifactId groupIdorg.apache.maven.scm/groupId version1.0-SNAPSHOT/version /parent groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-synergy/artifactId nameMaven SCM Synergy Provider/name version1.0-SNAPSHOT/version scm connection scm:svn:http://iliade.sud.capgemini.fr/svn/laposte/maven-scm-provider-ccm/trunk /connection developerConnection scm:svn:http://iliade.sud.capgemini.fr/svn/laposte/maven-scm-provider-ccm/trunk /developerConnection url ![CDATA[http://illiade.sud.capgemini.fr/websvn/listing.php?repname=La+Poste+-+Provider+SCM+Maven+Synergypath=%2Ftrunk%2Frev=0sc=0]] /url /scm pluginRepositories pluginRepository idMaven Snapshots/id urlhttp://people.apache.org/maven-snapshot-repository//url releases updatePolicydaily/updatePolicy /releases snapshots updatePolicydaily/updatePolicy /snapshots /pluginRepository /pluginRepositories build plugins plugin groupIdorg.codehaus.modello/groupId artifactIdmodello-maven-plugin/artifactId version1.0-alpha-6/version executions execution goals goaljava/goal goalxpp3-reader/goal goalxsd/goal /goals /execution /executions configuration version1.0.0/version modelsrc/main/mdo/synergy-settings.mdo/model /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId dependencies dependency groupIdorg.apache.maven.scm/groupId artifactId maven-scm-provider-synergy /artifactId version1.0-SNAPSHOT/version /dependency /dependencies /plugin /plugins /build /project Thanks -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l'Arénas -- Entrée B | 455 Promenade des Anglais | 06200 Nice **Join the Collaborative Business Experience ** _ This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: How to deal with modules
Nop, there is nothing in Working Directory nor in Build Output Directory. It's strange the pom is in /tmp. Should be in Working Directory/number... And yes, we are using a corporate proxy, but we have other projects that build fine on continuum, and this one build on my PC (I'm using the corporate proxy too). Emmanuel Venisse a écrit : Julien Henry a écrit : Hi, I'm working on a scm plugin for Synergy. I would like to put it on continuum in my company, but I get an error from continuum: Continuum Error * Cannot build maven project from /tmp/continuum/svn/laposte/maven-scm-provider-ccm/trunk/pom.xml (Cannot find parent: org.apache.maven.scm:maven-scm-providers for project: org.apache.maven.scm:maven-scm-provider-synergy:jar:1.0-SNAPSHOT). Check the logs for more details. Do you have more details in your logs? It seems it couldn't download the parent pom from the repo, do you use a proxy? Emmanuel Here is the pom : ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion parent artifactIdmaven-scm-providers/artifactId groupIdorg.apache.maven.scm/groupId version1.0-SNAPSHOT/version /parent groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-synergy/artifactId nameMaven SCM Synergy Provider/name version1.0-SNAPSHOT/version scm connection scm:svn:http://iliade.sud.capgemini.fr/svn/laposte/maven-scm-provider-ccm/trunk /connection developerConnection scm:svn:http://iliade.sud.capgemini.fr/svn/laposte/maven-scm-provider-ccm/trunk /developerConnection url ![CDATA[http://illiade.sud.capgemini.fr/websvn/listing.php?repname=La+Poste+-+Provider+SCM+Maven+Synergypath=%2Ftrunk%2Frev=0sc=0]] /url /scm pluginRepositories pluginRepository idMaven Snapshots/id urlhttp://people.apache.org/maven-snapshot-repository//url releases updatePolicydaily/updatePolicy /releases snapshots updatePolicydaily/updatePolicy /snapshots /pluginRepository /pluginRepositories build plugins plugin groupIdorg.codehaus.modello/groupId artifactIdmodello-maven-plugin/artifactId version1.0-alpha-6/version executions execution goals goaljava/goal goalxpp3-reader/goal goalxsd/goal /goals /execution /executions configuration version1.0.0/version modelsrc/main/mdo/synergy-settings.mdo/model /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId dependencies dependency groupIdorg.apache.maven.scm/groupId artifactId maven-scm-provider-synergy /artifactId version1.0-SNAPSHOT/version /dependency /dependencies /plugin /plugins /build /project Thanks -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice **Join the Collaborative Business Experience ** _ This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: How to deal with modules
) at org.apache.maven.continuum.DefaultContinuum.executeAddProjectsFromMetadataActivity(DefaultContinuum.java:804) at org.apache.maven.continuum.DefaultContinuum.addMavenTwoProject(DefaultContinuum.java:712) at org.apache.maven.continuum.web.action.AddMavenTwoProject.uponSuccessfulValidation(AddMavenTwoProject.java:52) at org.codehaus.plexus.formica.action.AbstractEntityAction.execute(AbstractEntityAction.java:136) at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:68) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108) at javax.servlet.http.HttpServlet.service(HttpServlet.java:615) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.maven.scm:maven-scm-providers' not found in repository: Unable to download the artifact from any repository org.apache.maven.scm:maven-scm-providers:pom:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:513) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1157) ... 31 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository org.apache.maven.scm:maven-scm-providers:pom:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:136) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:467) ... 32 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:260) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:124) ... 34 more 597186636 [SocketListener0-4] INFO org.apache.maven.continuum.Continuum - Created 0 projects. 597186636 [SocketListener0-4] INFO org.apache.maven.continuum.Continuum - Created 0 project groups. 597186636 [SocketListener0-4] INFO org.apache.maven.continuum.Continuum - 1 warnings. 597186636 [SocketListener0-4] INFO org.apache.maven.continuum.Continuum - Cannot build maven project from /tmp/continuum/svn/laposte/maven-scm-provider-ccm/trunk/pom.xml (Cannot find parent: org.apache.maven.scm:maven-scm-providers for project: org.apache.maven.scm:maven-scm-provider-synergy:jar:1.0-SNAPSHOT). Emmanuel Venisse a écrit : Where is defined your proxy on continuum machine? Julien Henry a écrit : Nop, there is nothing in Working Directory nor in Build Output Directory. It's strange the pom is in /tmp. Should be in Working Directory/number... And yes, we are using a corporate proxy, but we have other projects that build fine on continuum, and this one build on my PC (I'm using the corporate proxy too). Emmanuel Venisse a écrit : Julien Henry a écrit : Hi, I'm working on a scm plugin for Synergy. I would like to put it on continuum in my company, but I get an error from continuum: Continuum Error * Cannot build maven project from /tmp/continuum/svn/laposte/maven-scm-provider-ccm/trunk/pom.xml (Cannot find parent: org.apache.maven.scm:maven-scm-providers for project: org.apache.maven.scm:maven-scm-provider-synergy:jar:1.0-SNAPSHOT). Check the logs for more details. Do you have more details in your logs? It seems it couldn't download the parent pom from the repo, do you use a proxy? Emmanuel Here
Re: How to deal with modules
Hi, Thanks for you tips. The solution was to remove parent declaration, and to add the missing dependencies. But it could be easier if continuum was understanding parent pom... ++ Julien [EMAIL PROTECTED] a écrit : Hello, well, I found a way to build multi modules in continuum: 1- simply remove the modules in copy of the parent pom. 2- upload this copy 3. continuum will co from ccm all sources and build all modules in the same project, as result. But in your case, for my mind of course, the best way is removing the parent declaration, even if you should put in your folder structure the parent source... hope that it is helped you. regards, Andre -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: dinsdag 19 september 2006 10:15 To: continuum-users@maven.apache.org Subject: Re: How to deal with modules Julien Henry a écrit : Hi, I'm working on a scm plugin for Synergy. I would like to put it on continuum in my company, but I get an error from continuum: Continuum Error * Cannot build maven project from /tmp/continuum/svn/laposte/maven-scm-provider-ccm/trunk/pom.xml (Cannot find parent: org.apache.maven.scm:maven-scm-providers for project: org.apache.maven.scm:maven-scm-provider-synergy:jar:1.0-SNAPSHOT). Check the logs for more details. Do you have more details in your logs? It seems it couldn't download the parent pom from the repo, do you use a proxy? Emmanuel Here is the pom : ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion parent artifactIdmaven-scm-providers/artifactId groupIdorg.apache.maven.scm/groupId version1.0-SNAPSHOT/version /parent groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-synergy/artifactId nameMaven SCM Synergy Provider/name version1.0-SNAPSHOT/version scm connection scm:svn:http://iliade.sud.capgemini.fr/svn/laposte/maven-scm-p rovider-ccm/trunk /connection developerConnection scm:svn:http://iliade.sud.capgemini.fr/svn/laposte/maven-scm-p rovider-ccm/trunk /developerConnection url ![CDATA[http://illiade.sud.capgemini.fr/websvn/listing.php?re pname=La+Poste+-+Provider+SCM+Maven+Synergypath=%2Ftrunk%2Fr ev=0sc=0]] /url /scm pluginRepositories pluginRepository idMaven Snapshots/id urlhttp://people.apache.org/maven-snapshot-repository//url releases updatePolicydaily/updatePolicy /releases snapshots updatePolicydaily/updatePolicy /snapshots /pluginRepository /pluginRepositories build plugins plugin groupIdorg.codehaus.modello/groupId artifactIdmodello-maven-plugin/artifactId version1.0-alpha-6/version executions execution goals goaljava/goal goalxpp3-reader/goal goalxsd/goal /goals /execution /executions configuration version1.0.0/version modelsrc/main/mdo/synergy-settings.mdo/model /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId dependencies dependency groupIdorg.apache.maven.scm/groupId artifactId maven-scm-provider-synergy /artifactId version1.0-SNAPSHOT/version /dependency /dependencies /plugin /plugins /build /project Thanks This message is intended for the addressee or its representative only. Any form of unauthorized use, publication, reproduction, copying or disclosure of the content of this e-mail is not permitted. If you are not the intended recipient of this e-mail message and its contents, please notify the sender immediately and delete this message and all its attachments subsequently. -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice **Join
Re : Maven and Selenium?
Hi, It's true that jWebUnit API is not easier than Selenium-RC API (except some very usefull assertions). But one of it's main advantage is to be compatible with different testing engines. Once your tests are written with jWebUnit, they could be executed thanks to HtmlUnit on your integration server each night. And for example, before each delivery, you could run them with Selenium to check compatibility with your customer's web browser. ++ Julien - Message d'origine De : Ralph Pöllath [EMAIL PROTECTED] À : Maven Users List users@maven.apache.org Envoyé le : Jeudi, 10 Août 2006, 9h35mn 23s Objet : Re: Maven and Selenium? Hi, I understand that Selenium by design requires a full-fledged browser, but isn't that also one of its greatest features? By running your tests using FF or IE, you can be sure they do work in their target environment, regardless of browser bugs. So yes, the htmlunit approach makes testing easier to integrate with CI, but it doesn't give you the same results. This may be acceptable for many simple testcases though. I just looked over the jWebUnit 2.x website very quickly, so I may be missing something. But how is test case writing with jWebUnit easier than using Selenium's IDE or DSL syntax? Cheers, -Ralph. On 02.08.2006, at 10:02, Christophe DENEUX wrote: Hi Daniel, Some advantages of using jWebUnit to test a web application are: - easier test case writing, - faster test case running, - No graphic server is needed with the engine htmlunit, so the integration into a continuous integration system is easier (no browser is needed), - Soon, you will use an engine for Selenium to run your tests directly in your browser. jWebUnit home: http://jwebunit.sourceforge.net __ __ Christophe DENEUX / Capgemini Sud / Méditerranée Technical Leader Tel: + 33 4 93 72 43 74 / www.capgemini.com Fax: + 33 4 93 21 02 95 Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice Join the Collaborative Business Experience __ __ Daniel Serodio a écrit : Christophe DENEUX wrote: Hi , A snapshot repository is available at: http://maven.openqa.org/ Have you try jWebUnit (http://jwebunit.sourceforge.net/index.html) instead of Selenium for your functional tests? With jWebUnit, you can run your tests with different engines as htmlunit or Selenium (the Selenium engine is available trough SVN). You will use the htmlunit engine to execute your tests in a background mode (continuous integration) and the selenium engine in a visual mode. It's been a while since I looked at jWebUnit, and I'm currently using Selenium; what is the advantage of using jWebUnit as you describe instead of using Selenium directly? Do you have an URL with more info on the subject? TIA, Daniel Serodio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
