RE: Maven2-commons-logging-api jar isue
> We are running two maven (2.0.4) setups in our company. The problem is > that when it tries to download commons-logging-api jar (1.1) from > ibiblio it gives an error that pom not found as pom is not > available at > ibiblio. But the same jar can be downloaded on the other setup. commons-logging-api 1.1 artifact doesn't exist or was not uploaded by commons-logging developpers Use commons-logging 1.1 artifact instead Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven2-commons-logging-api jar isue
> > We are running two maven (2.0.4) setups in our company. The > problem is > > that when it tries to download commons-logging-api jar (1.1) from > > ibiblio it gives an error that pom not found as pom is not > > available at > > ibiblio. But the same jar can be downloaded on the other setup. > commons-logging-api 1.1 artifact doesn't exist or was not > uploaded by commons-logging developpers > > Use commons-logging 1.1 artifact instead More : http://www.mail-archive.com/commons-user@jakarta.apache.org/msg16106.html Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Surefire report issues
> Also, I noticed a problem with the surefire report contents. > It seems to > create a report that lists test results grouped together by > package and > class, but when you look closer you find tests from other > classes and even > other packages in the same group. http://jira.codehaus.org/browse/MSUREFIRE-114 Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Hibernate 3.2
To search artifacts : www.mvnrepository.com www.mvnregistry.com Very helpful Damien > -Message d'origine- > De : Mark Grand [mailto:[EMAIL PROTECTED] > Envoyé : mercredi 15 novembre 2006 17:13 > À : users@maven.apache.org > Objet : Hibernate 3.2 > > > I want to use Hibernate 3.2 in a project that I am building with > maven. There is no artifact for Hibernate 3.2 in ibiblio. How can I > manually set it up in my local repository? > > Mark Grand (404)925-8265 > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Release Plugin: Include assemblies for deploying
I'm doing releases like that : mvn release:perform -Dgoals="install assembly:attached deploy site-deploy" Beware, some phases are executed twice, even three times Damien > -Message d'origine- > De : Timo Wolf [mailto:[EMAIL PROTECTED] > Envoyé : jeudi 16 novembre 2006 12:15 > À : users@maven.apache.org > Objet : Release Plugin: Include assemblies for deploying > > > Hi All, > > I have a multi module project with some modules that include a > required assembly > to pack a complete application containing scripts, properties, etc. > > When making a release on the top level directory, all jars, and poms > etc get uploaded and > deployed on my repository. > > Is it possible to invoke the assembly goals from some modules from > the release plugin > and also deploy the packed applications in the repository. > > When I invoke mvn release:perform, I want to have all > artifacts in my > repository, including the > assemblies of some submodules. > > Thanks a lot > > Timo > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Hibernate 3.2
> WARN: Don't go to www.mvnregistry.com! It redirects to a place that > tries to install an exe for porn. (don't worry if you're on Mac OS X > or other un*x ;-)). > > Damien Lecan: I'm not amused. Sorry, I did not see that problem with mvnregistry.com Use the other one instead : www.mvnrepository.com Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Release Plugin: Include assemblies for deploying
Ok, I thought you were building your assembly at the top of your multi-module project. If you build assemmbly in specific projet, bind the assembly operation to the package phase of your module : http://maven.apache.org/plugins/maven-assembly-plugin/usage.html See "Building an Assembly as Part of the Build Lifecycle" in Damien > -Message d'origine- > De : Timo Wolf [mailto:[EMAIL PROTECTED] > Envoyé : jeudi 16 novembre 2006 14:42 > À : Maven Users List > Objet : Re: Release Plugin: Include assemblies for deploying > > > Hi, > > The problem with this line is, that I have a multi module > project and > call the > mvn release from the top level directory. I have only > assembly goals for > some submodules and the invocation of mvn assembly:assembly fails > from the top level directory. > > Any help about this probem? > > Thanks > > Timo > > [INFO] [assembly:attached] > [INFO] > -- > -- > [ERROR] BUILD FAILURE > [INFO] > -- > -- > [INFO] No assembly descriptors found. > [INFO] > -- > -- > [INFO] For more information, run Maven with the -e switch > [INFO] > -- > -- > [INFO] Total time: 6 seconds > [INFO] Finished at: Thu Nov 16 13:14:56 CET 2006 > [INFO] Final Memory: 5M/11M > > > On Nov 16, 2006, at 12:50 PM, LECAN Damien wrote: > > > I'm doing releases like that : > > > > mvn release:perform -Dgoals="install assembly:attached deploy site- > > deploy" > > > > Beware, some phases are executed twice, even three times > > > > Damien > > > >> -Message d'origine- > >> De : Timo Wolf [mailto:[EMAIL PROTECTED] > >> Envoyé : jeudi 16 novembre 2006 12:15 > >> À : users@maven.apache.org > >> Objet : Release Plugin: Include assemblies for deploying > >> > >> > >> Hi All, > >> > >> I have a multi module project with some modules that include a > >> required assembly > >> to pack a complete application containing scripts, properties, etc. > >> > >> When making a release on the top level directory, all > jars, and poms > >> etc get uploaded and > >> deployed on my repository. > >> > >> Is it possible to invoke the assembly goals from some modules from > >> the release plugin > >> and also deploy the packed applications in the repository. > >> > >> When I invoke mvn release:perform, I want to have all > >> artifacts in my > >> repository, including the > >> assemblies of some submodules. > >> > >> Thanks a lot > >> > >> Timo > >> > >> > >> > - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Release Plugin: Include assemblies for deploying
> I did this and it does not work. It only works when all dependencies > are already installed. I found in another > mail that binding the assembly to the package phase does not work in > a multi module project. > I must somehow configure maven to call mvn assembly:attached at the > top level so that > - for each subdirectory where an assembly is configured, the > assembly is invoked in that directory. > > In other words, > Instead of going in each sub directory and invoke mvn > assembly, I > just want to invoke it once > at the top level to integrate it in the release with one call. Can you describe in more details your project structure ? I don't understand how you can have sub-modules with assemblies (not on the top level of project) depending on other sub-modules that Maven reactor doesn't build before. Note : you can use assembly:single in a multi-module project Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to get default plugin configuration back ?
Hello, In my parent pom : maven-compiler-plugin 1.1 So, in child's projects, target is forced at 1.1 I can override configuration in child's pom : maven-compiler-plugin 1.5 But I don't really want 1.5, I just don't want to have parent's configuration. So, how to get default configuration back ? maven-compiler-plugin ?? Thank you Damien Lecan -- Telematic Systems B2i - Viveris Group France Tel : +33 (0)1 41 73 48 79 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven2 with VSS: Has maven scm plugin implemented scm:checkout for VSS?
Ask this question to Maven SCM mailing-lists http://maven.apache.org/scm/mail-lists.html Damien > -Message d'origine- > De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Envoyé : mardi 5 décembre 2006 05:19 > À : users@maven.apache.org > Objet : Maven2 with VSS: Has maven scm plugin implemented scm:checkout > for VSS? > > > > try command line "mvn scm:checkout" > > following error found, > Embedded error: No such command 'checkout' > > Anyone can help? Thanks! > > Regards, > Joy > > > > > > > > > IMPORTANT NOTICE > Email from OOCL is confidential and may be legally > privileged. If it is not intended for you, please delete it > immediately unread. The internet cannot guarantee that this > communication is free of viruses, interception or > interference and anyone who communicates with us by email is > taken to accept the risks in doing so. Without limitation, > OOCL and its affiliates accept no liability whatsoever and > howsoever arising in connection with the use of this email. > Under no circumstances shall this email constitute a binding > agreement to carry or for provision of carriage services by > OOCL, which is subject to the availability of carrier's > equipment and vessels and the terms and conditions of OOCL's > standard bill of lading which is also available at http://www.oocl.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Assembly question/bizarreness
This is a Maven problem http://jira.codehaus.org/browse/MNG-1682 Damien > -Message d'origine- > De : Hal Hildebrand [mailto:[EMAIL PROTECTED] > Envoyé : jeudi 14 décembre 2006 05:25 > À : users@maven.apache.org > Objet : Assembly question/bizarreness > > > I'm trying to get an assembly of all the artifacts built and > I'm running > into something odd. The project is multi-modules with > several levels. All > the artifacts are OSGi bundles generated using the Felix osgi > maven plugin. > But some of the artifacts are placed in the assembly using > the extension > ".osgi-bundle", while most of the others have the correct > ".jar" extension. > > When do the normal "clean install", the only artifacts I have > built have the > expected extensions of ".jar". However, invoking "clean package > assembly:assembly" at the top level causes these mystery > artifacts to come > into existence. Even stranger, these artifacts actually are > jars - i.e. If > I rename them with a ".jar" extension, they are the same > artifact I was > expecting... > > > I can't seem to find anything different about the poms... > They all have the > same osgi-bundle element. Yet, in my > assembly, I get > some with ".jar" and some with ".osgi-bundle". > > Here's my assembly descriptor: > > > modules > > jar > > > > > / > false > false > > > > > > I¹m sure I have to be doing something wrong, I just can¹t for > the life of me > see where it¹s happening... > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: junit4 support added
Hello, Use Surefire Plugin instead http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-surefire-plugin/2.3-SNAPSHOT/ Damien > -Message d'origine- > De : Zaphod [mailto:[EMAIL PROTECTED] > Envoyé : mardi 9 janvier 2007 11:50 > À : users@maven.apache.org > Objet : Re: junit4 support added > > > > Yes of course I use this repo url. > But I searched for a "2.3-SNAPSHOT" in this repo and didn't found it. > > I suppose surefire-junit4/2.1-SNAPSHOT/ is the one you mean, isn't it? > > But when I try to use > > > org.apache.maven.surefire > surefire-junit4 > 2.1-SNAPSHOT > > I get a > java.lang.NullPointerException > at > org.apache.maven.plugin.DefaultPluginManager.addPlugin(Default > PluginManager.java:292) > at > org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPl > ugin(DefaultPluginManager.java:198) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(Defa > ultPluginManager.java:163) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlug > in(DefaultLifecycleExecutor.java:1252) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPlugin > ToLifecycle(DefaultLifecycleExecutor.java:1216) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructL > ifecycleMappings(DefaultLifecycleExecutor.java:982) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa > l(DefaultLifecycleExecutor.java:453) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa > lAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTas > kSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(De > faultLifecycleExecutor.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(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > 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) > > If I try > > > org.apache.maven.surefire > surefire > 2.1-SNAPSHOT > > I get this: > [...] > Downloading: > http://people.apache.org/repo/m2-snapshot-repository/org/apach e/maven/surefire/surefire/2.1-SNAPSHOT/surefire-2.1-20070108.094711-11.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.surefire ArtifactId: surefire Version: 2.1-20070108.094711-11 Reason: Unable to locate resource in repository because there is no Jar-file inside. Tom Huybrechts wrote: > > It is. But you are pointing to the surefire directory inside that > repository. > You need to use http://people.apache.org/repo/m2-snapshot-repository/ > as repo url. > > On 1/8/07, Zaphod wrote: >> >> In which snapshot repository can I find it? >> I supposed it to be in >> http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/surefire/ >> >> >> Tom Huybrechts wrote: >> > >> > The snapshots have been deployed (maven-surefire-plugin version >> > 2.3-SNAPSHOT). >> > Read >> > >> http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html >> > for information on how to use them. > > -- View this message in context: http://www.nabble.com/junit4-support-added-tf2936023s177.html#a8235395 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cobertura-maven-plugin-2.1 is brokens?
> Hate the change mojo's root pom to pin down the version ;-) Time to correct the bug ? Several major bugs have been raised on this version (2.1) for a while, and no one works on them. http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=11226&fixfor=-1 And version 2.0 cannot be use in some multi-module applications because of http://jira.codehaus.org/browse/MCOBERTURA-39 (fixed in 2.1 ...) Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Proximity vs. Maven Achiva
> Once Archiva is stable, i think this is the one to go since > it has more features Any idea of when it will be stable ? Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Eclipse project files and maven-compiler-plugin configuration
Hello, I try to migrate an old project architecture to maven, and it works well. Here is the structure of one module : Module_root +- file1 +- file2 +- my +-company +- package +- Example.Java +- ... In my pom.xml : . ... maven-compiler-plugin my/** This config is ok, my artifact doesn't contain 'file1' and 'file2'. But, when I generate Eclipse project files, classpathentry in .classpath is not configured correctly : instead of How to configure maven-eclipse-plugin, or maven-compiler-plugin ? Thanks Damien Lecan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Unable to migrate from 1.0.2 to 1.0.3
> It seems you have something wrong in your settings.xml in > profile part. How to know what is it wrong ? It works perfectly with Continuum 1.0.2 (M2 2.0.4) Damien
RE: Unable to migrate from 1.0.2 to 1.0.3
> Can you send your settings.xml? /home/m2/repositories/local true http 192.168.128.254 3128 cvs.abcd.fr abcd.eu Repository de dev abcd http://cvs.abcd.fr:8080/repository central true central http://cvs.abcd.fr/repository true interval:120 true daily true abcd.plugins Repository de dev de plugins de abcd http://cvs.abcd.fr/maven2 > The NPE appears only in debug mode. You can change the log > level at the end of > apps/continuum/conf/application.xml with something like this: > > > > org.apache.maven.continuum.execution.maven.m2.Maven > BuilderHelper > INFO > I put DEBUG instead of INFO, restart Continuum, by stack trace remains the same. No additionnal information appear.
RE: Unable to migrate from 1.0.2 to 1.0.3
I added last night profile id and repository names in settings.xml: it works now. Why is Continuum so strict with settings.xml ? (eg : Maven works perfectly without profile id) Additionaly, build history is still missing. Damien
[Release plugin] Dependency versions not updated in rewrite-for-development phase
Hello, I'm working with Maven 2.0.4 and maven-release-plugin 2.0-beta4. When I try to release a multi-module project, the rewrite-for-development phase forgets to migrate dependency versions. For example : ## Before vsi vsi 0.0.2-SNAPSHOT 4.0.0 vsi plugin-generator Plugin generator 0.0.2-SNAPSHOT vsi canprovider-generator 0.0.2-SNAPSHOT provided ## Rewrite for release phase : OK All 0.0.2-SNAPSHOT references are converted to 0.0.2, even for dependencies ## Rewrite for development Errors appear, since the plugin forget to convert again dependency versions !! Here is the result : vsi vsi 0.0.3-SNAPSHOT 4.0.0 vsi plugin-generator Plugin generator 0.0.3-SNAPSHOT vsi canprovider-generator 0.0.2 provided Is it a bug, or something is wrong in my multi-module configuration ? Thanks Damien Lecan -- Telematic Systems B2i - Viveris Group France - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase
> Is artifact vis:canprovider-generator in reactors of the parent pom ?
Yes, thanks to "module" declaration in pom parent.
> I suggest you using dependencyManagement to manage
> dependencies beetwen
> reactors in a multi modules build.
> Because in this case you just need to change only one pom. (actually a
> by hand change is needed)
Ok, release:prepare and perform works with that. I used ${pom.version} instead
of version label in pom parent for dependencyManagement, and I worked perfectly
(nothing to change by hand after release).
Thanks
Damien
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase
> This patch rewrite poms for dev phase with next dev version for > dependencies in reactors. How to know if a module is in the reactor ? Because it appears in section ? Because it appears in section ? If this is the second solution, is there a link between the name of the folder's project and the name specified in the pom of this project ? Thanks Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Assembly and multi-levels multi-modules
Hello, I'm using maven-assembly-plugin with multi-modules projects, and it works fine for "flat" hierachy. I mean for multi-modules projects as : Parent +- Submodule1 +- Submodule2 But for this kind of layout : Parent:pom +- Submodule1:jar +- SubParent:pom +- Subsubmodule1:jar +- Subsubmodule2:jar I am not able to build an assembly with all referenced modules (Submodule1, Subsubmodule1 and Subsubmodule2). Moreover, assembly plugin tries to include module SubParent whereas it is a pom module ! How to assemble all my project ? Is it possible to exclude all pom modules from assembly ? (without specifiying exclusion for each in assembly descriptor) Thanks Damien Lecan -- Telematic Systems B2i - Viveris Group France - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Assembly and multi-levels multi-modules
> Not 100% sure on this, but what if you try to make 2 > assemblies here? the first one for the subsub-modules (inside > the subparent) > and the second one with the result of the subparent > (=assembly of subsub-modules) and submodule? > Not sure on how to do this, but it seems kind of logical this > way to me... Yes it is logical, but I have much more than 2 multi-modules levels I can't build an assembly for each level. Finally, I would need to merge all them at the end, and I don't know how I could do that. Thanks Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Assembly and multi-levels multi-modules
> > Not 100% sure on this, but what if you try to make 2 assemblies > > here? the first one for the subsub-modules (inside the subparent) > > and the second one with the result of the subparent (=assembly of > > subsub-modules) and submodule? > > Not sure on how to do this, but it seems kind of logical this way > > to me... > > I think this is a really cool idea I tried to do it for my > project but unfortunately I couldn't find a way to reference the > assembly of the subModule in the moduleSet of the parent > module. The > submodule assembly gets set as an 'attached' artifact and not the > main one.. by the tag in the moduleSet only supports the > main modules. If we could add the classifier's on this would work > very well I think! I looked at the code and a kind of filter restricts the content of the reactor (in AbstractAssemblyMojo#getModulesFromReactor(MavenProject, boolean), with method isProjectModule(...)). If I remove this filter, I get everything I need in my assembly. But this should produce issues in the special cases I think. I think I will fill a new jira issue for that. Damien Lecan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Java2HTML plugin M2
Hello, It seems to be a M1 plugin, not M2 ... Damien > -Message d'origine- > De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Envoyé : lundi 26 juin 2006 14:49 > À : users@maven.apache.org > Objet : Java2HTML plugin M2 > > > Hi, > Has anyone had any success working with Java2HTML plugin and M2 ? > I get NullPointer exception when trying to install plugin to > my repository as per instructions from > http://www.qualitylabs.org/java2htmlplugin/index.html > Tx > Andy > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Emma plugin for maven 2.0
> I am confused whether emma plugin for maven 2.0 is really available or > not... > If anybody knows about this, then please let me know... According to this page http://emma.sourceforge.net/maven-emma-plugin/ this plugin is only avalaible for M1. Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Possibility to define central mirror on command line ?
Hi, I would like to define a new mirror of "central" on mvn command line. Is it possible ? Otherwise, where is configured url of "central" repository (ibiblio I guess) en maven distribution ? I don't want to use settings.xml configuration. Thanks Damien Lecan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Possibility to define central mirror on command line ?
> Currently you can only use settings.xml. Why don't you want to use > settings.xml? Arghh, because maven embedder doesn't use it and I'm looking for a workaround for maven eclipse plugin limitation. So, I will build my own maven or maven embedder in order to use my own internal repository instead of repo1.maven.org Is it hard coded in a java file or is it located in a properties file ? Thanks Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Possibility to define central mirror on command line ?
> The embedder now uses it. It will align itself to a user > installation if it exists. Waoh ! In maven-2.0.3-snapshot or maven-2.1.0-snapshot ? Thanks Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to force download of internal snapshots ?
Hello, I work with maven 2.0.2 in a corporate environment with a maven-proxy for ibibli and co. and for our internal repository of releases and snapshots. Everything work fine with external artifacts and internal released artifacts. But for internal snapshots, maven refuses to download them. It always looks for them in each local developer repositories. How to force maven to download snapshots ? Thanks Damien Lecan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Assembly including binaries: Bug on a n depth hierarchy
Hello, This problem has already been reported : http://jira.codehaus.org/browse/MASSEMBLY-117 Vote for it :) > Unfortunately this always fails into an exception: "pom:pom1.1 does not > have an artifact with a file. Please ensure the package phase (...)" You can avoid this problem by excluding theses modules with 'pom' packaging. > Thanks in advance if you have any workaround. For the recursion problem, I made my own assembly plugin release (with the patch provided in the bug report). Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] ant run plugin
Hello Just add that in your pom ... org.apache.maven.plugins maven-source-plugin jar ... This will build a source jar each time you build your application jar file Damien > -Message d'origine- > De : Frederik Bayart [mailto:[EMAIL PROTECTED] > Envoyé : lundi 7 août 2006 17:53 > À : Maven Users List > Objet : RE: [m2] ant run plugin > > > see http://maven.apache.org/plugins/maven-antrun-plugin/usage.html > > > > > > > > > > -Original Message- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Monday, August 07, 2006 8:39 AM > To: Maven Users List > Subject: Re: [m2] ant run plugin > > Maven does not invoke Ant from Ant's installed directory. Instead it > downloads the Ant libs to the Maven repo and uses them directly. > > You will need to install your WS lib in the Maven repo and > specify it as > a on the Ant plugin, so that Maven includes it when running your > Ant commands. > > Wayne > > On 8/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi > > > > > > > > > classname="com.ibm.websphere.ant.tasks.WsEjbDeploy" /> > > > > I have a problem defining the ant run. I have copied the > Ant tasks to > > the ANT_1.6.5\lib directory, but Ant does not seem to know > where the > > external ant task? How is M2 invoking Ant? > > > > -- > > Peter Pilgrim > > UBS Investment Bank, > > PTS Portal / IT FIRC OPS LDN, > > 100 Liverpool Street, London EC2M 2RH, United Kingdom > > :: Java EE / E-Commerce / Enterprise Integration / Development :: > > > > Visit our website at http://www.ubs.com > > > > This message contains confidential information and is intended only > > for the individual named. If you are not the named addressee you > > should not disseminate, distribute or copy this e-mail. > Please notify > > > the sender immediately by e-mail if you have received this > e-mail by > > mistake and delete this e-mail from your system. > > > > E-mail transmission cannot be guaranteed to be secure or > error-free as > > > information could be intercepted, corrupted, lost, > destroyed, arrive > > late or incomplete, or contain viruses. The sender > therefore does not > > > accept liability for any errors or omissions in the > contents of this > > message which arise as a result of e-mail transmission. If > > verification is required please request a hard-copy version. This > > message is provided for informational purposes and should not be > > construed as a solicitation or offer to buy or sell any > securities or > > related financial instruments. > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > _ > Scanned on 07 Aug 2006 15:44:06 > Scanned by Erado > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Packaging all modules as Jar
Hello > The version you're using doesn't "easily" support what you want to > accomplish. You might want to try the 2.1 version or maybe > the snapshot version 2.2-SNAPSHOT. Where to find org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7-SNAPSHOT ? It doesn't seem to be deployed either on people.apache.org/maven-snapshot-repository or on snapshots.maven.codehaus.org/maven2 Thanks Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : [solved] product codes at java 1.4, test sources at java 1.5
Waoh, good job. Your special configuration gave me a lot of ideas (Especially
section in plugin configuration)
Thanks
Damien Lecan
Message d'origine
De: Nicolas De Loof [mailto:[EMAIL PROTECTED]
Date: jeu. 07/09/2006 17:33
À: Maven Users List
Objet : [solved] product codes at java 1.4, test sources at java 1.5
Here is my POM :
org.apache.maven.plugins
maven-compiler-plugin
1.3
1.3
${settings.localRepository}/com/sun/rt/1.3.1_08/rt-1.3.1_08.jar
compile-tests
process-test-sources
testCompile
1.5
1.5
${java.home}/lib/rt.jar
com.sun
rt
1.3.1_08
Nico.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to set: No Scheduled build | Only triggered build
Create a disabled schedule ! (uncheck "enable") Call it "No schedule", and project won't be build anymore. Damien > -Message d'origine- > De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Envoyé : mardi 12 septembre 2006 09:27 > À : continuum-users@maven.apache.org > Objet : Re: How to set: No Scheduled build | Only triggered build > > > If you set the year of the schedule to something in the > future like 2050, the schedule won't be > executed. > > Emmanuel > > Anoop kumar V a écrit : > > Ohh really?? > > > > I have this issue - we have a dev env and a test env. The > DEV is more or > > less like an integration environment for all developers. > The TEST env is > > where we finally push code for testing by a separate testing team > > > > We have set these 2 envs as 2 different projects in > Continuum. The latest > > from CVS is picked up and a build is made for each. > > > > But if a release is going on, and the test team is testing > a release (ON > > TEST), we wouldnt want to build / deploy into TEST (and > mess up the env) - > > but it is ok if a build happens on DEV. So we all agreed > (TEST and DEV > > teams) that we will henceforth use Continuum to do only 'on > demand' builds > > (only if triggered by the user)and there would be no > scheduled builds. > > > > How can I work around this issue? One way as I have > mentioned below is to > > specify a very large quiet period > > The other option maybe is to maintain a branch in CVS which > will be used > > only for TEST, and merge from HEAD into this BRANCH just > when we want to > > build / deploy into stuff.. > > > > Is there some other easier way that I might not have > thought about? (like > > maybe I can tweak the cron intervals to ensure that a build > never happens?? > > Our testing cycle never goes beyond a week!) > > > > Thanks a lot, > > Anoop > > > > On 9/12/06, Barrie Treloar <[EMAIL PROTECTED]> wrote: > >> > >> I don't think this feature is available currently. > >> > >> On 9/12/06, Anoop kumar V <[EMAIL PROTECTED]> wrote: > >> > Hi - Can somebody please help me a bit? > >> > > >> > Thanks, > >> > Anoop > >> > > >> > On 9/11/06, Anoop kumar V <[EMAIL PROTECTED]> wrote: > >> > > > >> > > Actually - the other way I have tried (not sure if it > works yet) > >> is to > >> > > just disable all the schedules that I have. So that > would only let a > >> user > >> > > click on the build-now link to build. Otherwise a > build would never > >> happen. > >> > > > >> > > -Anoop > >> > > > >> > > On 9/11/06, Anoop kumar V <[EMAIL PROTECTED]> wrote: > >> > > > > >> > > > Hi Continuum users, > >> > > > > >> > > > What is the best way to set the build schedule as > never. Only > >> when a > >> > > > user triggers, should the build happen?? > >> > > > > >> > > > As of now, I have created a new schedule with the > quiet period as a > >> very > >> > > > large time: 99. > >> > > > > >> > > > But this is not foolproof. Is there an option I can set? > >> > > > > >> > > > -- > >> > > > Thanks and best regards, > >> > > > Anoop > >> > > > > >> > > > >> > > > >> > > > >> > > -- > >> > > Thanks and best regards, > >> > > Anoop > >> > > > >> > > >> > > >> > > >> > -- > >> > Thanks and best regards, > >> > Anoop > >> > > >> > > >> > > > > > > > >
RE: Release plugin
Vote for this bug to http://jira.codehaus.org/browse/MRELEASE-110 "release:prepare generates tags with dots, causing problems with CVS" Damien > -Message d'origine- > De : Yann Le Du [mailto:[EMAIL PROTECTED] > Envoyé : mardi 12 septembre 2006 11:01 > À : Maven Users List > Objet : Re: Release plugin > > > For now, there doesn't seem to be a way to do so, but you can vote for > http://jira.codehaus.org/browse/MRELEASE-159 if you like. > > 2006/9/12, Adrian Pillinger <[EMAIL PROTECTED]>: > > > > Is there a way to customize the SCM tag name that is suggested by > > default when you run release:prepare? > > > > e.g it currently defaults to - > > > > I would like to remove the '.' characters in the version as CVS > > doesn't support them in tags. > > > > - > > This message (including any attachments) may contain confidential > > information intended for a specific individual and purpose. If you > > are not the intended recipient, delete this message. If you are > > not the intended recipient, disclosing, copying, distributing, or > > taking any action based on this message is strictly prohibited. > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Prepare after dryRun does not tag the scm
Hello > As mentionned in the Better Builds with Maven book, I am > trying to cut a > release. To do so, i first run "mvn release:prepare -DdryRun" > and if this is > ok I run "mvn release:prepare". > > If I do so, the second release:prepare call does not tag my > scm, thus the > "release:perform" cannot be done. Is there something I am not > doing right ? Do a release:clean between the executions of release:prepare, or do the second release:prepare with -Dresume=false parameter. Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Database Initialization Prior to Testing
> I've considered, but rejected, DBunit since the dbunit plugin doesn't > apparently exist for Maven2 Why do you need a maven plugin to use DBUnit ? It's an extension of JUnit, run it as a JUnit test ! It doesn't work ? Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Database Initialization Prior to Testing
> I want to make the database set up part of the integration tests as > external as possible to the test cases themselves, governed as part of > the build process associated with integration tests. You need your own framework, with configuration of what to do before, after each test class only when you want. JUnit 4, TestNG or AOP can help you I think Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
