Re: Calling ant tasks from maven pom
Niranjan Deshpande schrieb: Tim i indeed wht u suggested but the build xmls just dont seem to to reached.. It's working for me with this test project: . |-- pom.xml `-- src `-- main |-- antscripts | |-- antscript1.xml | `-- antscript2.xml `-- java relevant snippet from pom.xml: org.apache.maven.plugins maven-antrun-plugin hello-from-ant generate-sources run target="printhello"/> target="printhello"/> When invoking maven with a phase liek 'mvn package' tha ant tasks get executed during the spcified 'generate-sources' phase. And when invoking the antrun-plugin directly via 'mvn antrun:run' the scripts get called, too. As you see I used the default section outside of the . If you don't need to invoke the ant scripts standalone, I would move the configuration back inside the defined execution. -Tim On Thu, Jun 5, 2008 at 6:53 PM, Tim Kettler <[EMAIL PROTECTED]> wrote: Hi, (again :-) ) Niranjan Deshpande schrieb: I am trying to execute ant tasks from maven's pom as below. maven-antrun-plugin 1.1 generate-sources run The generate.sh file has 10 xml files that i want to run as ant -buildfile -filename for the time being I am running the plugin as maven antrun:run, just to find whether the .sh file is called or not. But i am geting this: [INFO] [antrun:run] [INFO] Executing tasks [INFO] Executed tasks I have added a ECHO in the .sh file, but i see none at the output First to answer your concrete problem: When you call a plugin goal directly from the commandline it uses the common configuration under as there may be more than one execution defined and there is no sane way to decide which ones configuration to use. Secondly, just to recap that I understood correctly what you are doing: You have a maven build from which you want to call a shell script which in turn triggers a few ant builds?!? Cant you just configure multiple calls of the task [1] in your antrun-plugin configuration and throw away the shell script completely? -Tim [1] http://ant.apache.org/manual/CoreTasks/ant.html - 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]
Surefire - Copying test files to target/test-classes
Hi everyone I have a small problem executing my JUnit test which depend on some test files (xml and plaintext documents). Whenever I run surefire compiles all JUnit Testclasses to target/test-classes but my test files don´t get copied to target/test-classes and therefore my JUnit tests fail. Now here is my question. How can I get maven2 to copy also my *.xml/*.txt to target/test-classes? Here is a snippet from my pom.xml. I have tried to use additionalClasspathElements but it did not work up to now. org.apache.maven.plugins maven-surefire-plugin C:\data\svn_pws\aktentemplate\trunk\server\core\src\test\java\de\corag\bpm\recordmgmt\domain\metadata\IvvSampleMetaData01Test.xml C:\data\svn_pws\aktentemplate\trunk\server\core\src\test\java\de\corag\bpm\recordmgmt\validation\java2xml\ivv-sample-01.xml C:\data\svn_pws\aktentemplate\trunk\server\core\src\test\java\de\corag\bpm\recordmgmt\validation\java2xml\IvvSample01Test_MetaData.xml Best regards, Silvio -- View this message in context: http://www.nabble.com/Surefire---Copying-test-files-to-target-test-classes-tp17685305p17685305.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Simple question - but totally frustrated - best way to define internal repo - but easily not use this repo when not at work?
I'm still a bit confused though... can't I define my repository in a parent.pom ? Why isn't this the preferred approach? Would seem to make sense to me - users check out a parent project from cvs. Run mvn install, put the parent pom in their repo. All new projects use this parent pom definition where the company's internal repo is definied. Wouldn't this be easier? On Thu, Jun 5, 2008 at 11:43 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > The easiest would be to simply rename settings.xml to settings.x when > you get home. This assumes that you don't have any special settings > for your projects. But this would disable the artifactory repo. Or if > you're on an operating system with symbolic links, you could adjust > the link to settings.xml when you change locations. > > Another approach would involve creating copies of mvn.bat and > settings.xml and calling mvn-copy when you're home. You would also set > mvn-copy.bat up to append -s /path/to/settings-copy.xml to all calls > to mvn. > > Wayne > > On Thu, Jun 5, 2008 at 10:06 PM, Rick <[EMAIL PROTECTED]> wrote: > > I'm totally confused and could use some help... > > > > I have an internal company repo setup fine. Currently, following the > > artifcatory docs, I defined this repo in my mavenhome/conf/settings.xml > file > > such as: > > > > > >acme-company > > > > > >central > >http://urlip:8081/artifactory/repo > > > >false > > > > > > > > > > I can then set this profile to be active in the settings.xml file as well > > and all works fine. > > > > The problem is when I'm at home using this laptop I don't want to use > this > > profile! I just want plain jane vanilla iblio repo. > > > > I'm confused how to set up things to get what I want - projects using our > > company parent pom using the repositories as defined above, and any other > > projects to not use the profile as above. > > > > What I was 'thinking' I could so is just set up the repository definition > in > > my parent proejct pom.. but that didn't seem to work at all. To me this > > makes the most sense as users wouldn't even have to define anything in > their > > settings.xml file. I see no examples of this however and can't seem to > get > > ti to work. Assuming I keep this profile definition in my (and > unfortunately > > the whole team's local settings.xml file) how do I set up parent company > > profile to use it? If I keep it "alawys active" then it's always active > even > > when I'm not at work which seems to be a pain. > > > > Even if this kind of info shouldn't be in a parent pom, and should be in > the > > settings.xml file, how do I then easily set things up so that I can do > "mvn > > install" when I'm not at work and have it NOT try to connect to the > > acme-company profile? I'd prefer not to have a pass in a profile argument > on > > the command line, but I suppose if I have to, I'll do it. > > > > I'm thinking this is a common situation so I must be totally doing > something > > wrong, > > > > -- > > Rick > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Rick
Re: java.net.SocketException - need help in getting started
Thank you! that was exactly the issue, all working now. -Gianni On 05/giu/08, at 07:29, Tim Kettler wrote: Hi, googling hints that it's a bug in the java sdk on freebsd. There is a similar bug report like yours for freebsd 6 posted for IDEA [1] which says that IPv6 support in the jdk is the problem. This [2] is another bug report of the same problem with the solution to set the JAVAVM_OPTS like this: export JAVAVM_OPTS_java=-Djava.net.preferIPv4Stack=true" And finally this bug was reported [3] on the freebsd-java list some time ago. Hope this helps -Tim [1] http://www.jetbrains.net/jira/browse/IDEA-15976 [2] http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2007-11/msg00220.html [3] http://lists.freebsd.org/pipermail/freebsd-java/2007-August/006544.html Gianni Doe schrieb: Hi, I'm completely new to maven and just trying out the "Maven in 5 Minutes" but not getting very far. When I try to create a new project I get the exception below; my machine has unimpeded access to the internet so the issue is not firewall related. I'd appreciate some suggestions. [EMAIL PROTECTED]:/data/Projects$ mvn -X archetype:create - DgroupId=com.test -DartifactId=testapp + Error stacktraces are turned on. Maven version: 2.0.9 Java version: 1.6.0_03-p4 OS name: "freebsd" version: "7.0-stable" arch: "amd64" Family: "unix" [DEBUG] Building Maven user-level plugin registry from: '/home/ shares/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/usr/ local/apache-maven/conf/plugin-registry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file [DEBUG] Exception org.apache.maven.wagon.TransferFailedException: Error transferring file at org .apache .maven .wagon .providers .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java: 104) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java: 68) at org .apache .maven .artifact .manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java: 470) at org .apache .maven .artifact .manager .DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java: 370) at org .apache .maven .artifact .repository .metadata .DefaultRepositoryMetadataManager .resolve(DefaultRepositoryMetadataManager.java:97) at org .apache .maven .plugin .DefaultPluginMappingManager .loadPluginMappings(DefaultPluginMappingManager.java:103) at org .apache .maven .plugin .DefaultPluginMappingManager .loadPluginMappings(DefaultPluginMappingManager.java:87) at org .apache .maven .plugin .DefaultPluginMappingManager .getByPrefix(DefaultPluginMappingManager.java:61) at org .apache .maven .plugin .DefaultPluginManager .getPluginDefinitionForPrefix(DefaultPluginManager.java:154) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .getMojoDescriptor(DefaultLifecycleExecutor.java:1468) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java: 405) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java: 137) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) 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:597) 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) Caused by: java.net.SocketException: Invalid argument at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at sun.net.NetworkClient.doConnect(NetworkClient.java:157) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.(HttpClient.java:233) at sun.net.ww
Re: Simple question - but totally frustrated - best way to define internal repo - but easily not use this repo when not at work?
On Thu, Jun 5, 2008 at 11:43 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > Or if you're on an operating system with symbolic links, you could adjust > the link to settings.xml when you change locations. > Ok, thanks. I can do the above. -- Rick
Re: Simple question - but totally frustrated - best way to define internal repo - but easily not use this repo when not at work?
The easiest would be to simply rename settings.xml to settings.x when you get home. This assumes that you don't have any special settings for your projects. But this would disable the artifactory repo. Or if you're on an operating system with symbolic links, you could adjust the link to settings.xml when you change locations. Another approach would involve creating copies of mvn.bat and settings.xml and calling mvn-copy when you're home. You would also set mvn-copy.bat up to append -s /path/to/settings-copy.xml to all calls to mvn. Wayne On Thu, Jun 5, 2008 at 10:06 PM, Rick <[EMAIL PROTECTED]> wrote: > I'm totally confused and could use some help... > > I have an internal company repo setup fine. Currently, following the > artifcatory docs, I defined this repo in my mavenhome/conf/settings.xml file > such as: > > >acme-company > > >central >http://urlip:8081/artifactory/repo > >false > > > > > I can then set this profile to be active in the settings.xml file as well > and all works fine. > > The problem is when I'm at home using this laptop I don't want to use this > profile! I just want plain jane vanilla iblio repo. > > I'm confused how to set up things to get what I want - projects using our > company parent pom using the repositories as defined above, and any other > projects to not use the profile as above. > > What I was 'thinking' I could so is just set up the repository definition in > my parent proejct pom.. but that didn't seem to work at all. To me this > makes the most sense as users wouldn't even have to define anything in their > settings.xml file. I see no examples of this however and can't seem to get > ti to work. Assuming I keep this profile definition in my (and unfortunately > the whole team's local settings.xml file) how do I set up parent company > profile to use it? If I keep it "alawys active" then it's always active even > when I'm not at work which seems to be a pain. > > Even if this kind of info shouldn't be in a parent pom, and should be in the > settings.xml file, how do I then easily set things up so that I can do "mvn > install" when I'm not at work and have it NOT try to connect to the > acme-company profile? I'd prefer not to have a pass in a profile argument on > the command line, but I suppose if I have to, I'll do it. > > I'm thinking this is a common situation so I must be totally doing something > wrong, > > -- > Rick > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Simple question - but totally frustrated - best way to define internal repo - but easily not use this repo when not at work?
I'm totally confused and could use some help... I have an internal company repo setup fine. Currently, following the artifcatory docs, I defined this repo in my mavenhome/conf/settings.xml file such as: acme-company central http://urlip:8081/artifactory/repo false I can then set this profile to be active in the settings.xml file as well and all works fine. The problem is when I'm at home using this laptop I don't want to use this profile! I just want plain jane vanilla iblio repo. I'm confused how to set up things to get what I want - projects using our company parent pom using the repositories as defined above, and any other projects to not use the profile as above. What I was 'thinking' I could so is just set up the repository definition in my parent proejct pom.. but that didn't seem to work at all. To me this makes the most sense as users wouldn't even have to define anything in their settings.xml file. I see no examples of this however and can't seem to get ti to work. Assuming I keep this profile definition in my (and unfortunately the whole team's local settings.xml file) how do I set up parent company profile to use it? If I keep it "alawys active" then it's always active even when I'm not at work which seems to be a pain. Even if this kind of info shouldn't be in a parent pom, and should be in the settings.xml file, how do I then easily set things up so that I can do "mvn install" when I'm not at work and have it NOT try to connect to the acme-company profile? I'd prefer not to have a pass in a profile argument on the command line, but I suppose if I have to, I'll do it. I'm thinking this is a common situation so I must be totally doing something wrong, -- Rick
Re: Managing SCM branching of large, multiple-releasable-artifacts Maven projects: ideas?
we manage the versioning problem by using one version for all projects. for a maven release we let maven auto increment the version number. merging back into the trunk we use svn merge, but sometimes there are conflicts with poms. --- On Thu, 6/5/08, Bryan Loofbourrow <[EMAIL PROTECTED]> wrote: > From: Bryan Loofbourrow <[EMAIL PROTECTED]> > Subject: Managing SCM branching of large, multiple-releasable-artifacts Maven > projects: ideas? > To: "Maven Users List" > Date: Thursday, June 5, 2008, 3:55 PM > I'm working with Maven on a large project == many, many > Maven projects, > and multiple, separately releasable artifacts. Managing > this is pretty > reasonable, but the part I haven't figured out how to > manage efficiently > has to do with branching in my source control manager. > > > > Let's take a typical branching scenario: I want to > branch the entire > source tree, work on the branch for a while, release the > branch > artifacts under some appropriate version, then merge the > changes back to > the main trunk. In the meantime, it's likely enough > that I've done a > release from the main trunk. > > > > This is all fine, except when it comes to those version > numbers in all > of the myriad pom.xml files. That's a bit of a merge > nightmare. > > > > I can't be the only person running into this. How do > you manage this > sort of thing? > > > > Thanks, > > > > -- Bryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Managing SCM branching of large, multiple-releasable-artifacts Maven projects: ideas?
I'm working with Maven on a large project == many, many Maven projects, and multiple, separately releasable artifacts. Managing this is pretty reasonable, but the part I haven't figured out how to manage efficiently has to do with branching in my source control manager. Let's take a typical branching scenario: I want to branch the entire source tree, work on the branch for a while, release the branch artifacts under some appropriate version, then merge the changes back to the main trunk. In the meantime, it's likely enough that I've done a release from the main trunk. This is all fine, except when it comes to those version numbers in all of the myriad pom.xml files. That's a bit of a merge nightmare. I can't be the only person running into this. How do you manage this sort of thing? Thanks, -- Bryan
Re: Advice how to structure a project I want to move to maven...
Well, this is actually an J2EE project (EJB3 to be specific)... But my questions remain even for a J2EE project? 2008/6/6 Mick Knutson <[EMAIL PROTECTED]>: > I always use multi-module, but I always am working on J2EE apps. > If you want common shared projects, then split this up, but you still might > have multi-modules if you are creating j2ee apps. > > > > On Thu, Jun 5, 2008 at 3:22 PM, Kent Närling <[EMAIL PROTECTED]> > wrote: > > > 2008/6/6 Mick Knutson <[EMAIL PROTECTED]>: > > > > > dist is usually going to be an assembly, and you add assembly > descriptors > > > into src/assemble/*.xml > > > You do not store the rpm's or bin's there. They do not end up in svn in > > > other words. > > > > > > I have: > > > root pom.xml > > > |-->common 1..* jar's > > > |-->core > > > |-->src > > > |-->assemble > > > |-->main/resources > > > |-->site > > > |-->/xdoc/**.* (docs) > > > |-->tools > > > |-->webapps 1..* wars > > > > > > > So common, core, tools, webapps etc would be modules of the main project? > > So you all seem to recommend creating a module based layout? > > > > Maybe I expressed myself a bit unclear, I never meant that the dist > > CONTAINED RPM:s or so! > > I mean that it's CREATES RPM:s etc ;-) > > > > In a module based layout like this, what if I then want to work on a > module > > (ie a plugin etc) without having to checkout the main project? > > Maybe I don't even have access to it? (only the jar:s) > > > > Also, what if we would like to release a separate version of a module > > outside of a release? (ie a patch or a feature without having to do a > > release cycle for the whole product) > > I can only imagine that it will be a bit "messy" in SVN then? since the > > modules won't have separate trunk:s and tag:s etc? or? > > > > > > > > > > On Thu, Jun 5, 2008 at 3:01 PM, Kent Närling <[EMAIL PROTECTED] > > > > > wrote: > > > > > > > Sorry, didn't get what you mean by that? > > > > > > > > You mean dist should not be a project on its own, or? > > > > > > > > > > > > 2008/6/5 Mick Knutson <[EMAIL PROTECTED]>: > > > > > > > > > dist should be src/assemble for assemblies. > > > > > > > > > > On Thu, Jun 5, 2008 at 2:41 PM, Kent Närling < > > [EMAIL PROTECTED] > > > > > > > > > wrote: > > > > > > > > > > > We have a project in SVN that is made of several projects, > > something > > > > like > > > > > > this: > > > > > > > > > > > > - core - core project > > > > > > - common - common libraries > > > > > > - pluginA > > > > > > - pluginB > > > > > > ... etc > > > > > > - doc - for documentation) > > > > > > - tools - some command line tools > > > > > > - dist - distribution project which packages all of the above > > > projects > > > > > into > > > > > > one or more packages (RPM:s for instance) > > > > > > > > > > > > Most of the the projects generate jar:s, but some generate EAR:s. > > > > > > > > > > > > Now on one hand we could create a main project with modules, but > > that > > > > > ties > > > > > > the modules so tightly to the main project, or? > > > > > > And the plugins (and future plugins) we would like to be able to > > give > > > > to > > > > > > third-party resources etc and they should not have access to most > > > core > > > > > > sources etc > > > > > > Additionally, if we put modules in subdirectories in SVN (as > > > > recommended) > > > > > > it > > > > > > becomes more awkward to release separate versions of the modules? > > > > > > > > > > > > At the end it should be easy to build the whole project and > package > > > it, > > > > > for > > > > > > instance automatically from within continuum for instance. > > > > > > Additionally, for developers it should be easy to check out all > > > > projects > > > > > > automatically and recursively into Eclipse... > > > > > > > > > > > > Any suggestions about the best strategy for a project like this? > > > > > > > > > > > > //Kent > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > --- > > > > > Thank You… > > > > > > > > > > Mick Knutson > > > > > BASE Logic, inc. > > > > > > > > > > Website: http://baselogic.com > > > > > Blog: http://baselogic.com/blog > > > > > BLiNC Magazine: http://blincmagazine.com > > > > > Linked IN: http://linkedin.com/in/mickknutson > > > > > DJ Mick: http://djmick.com > > > > > MySpace: http://myspace.com/mickknutson > > > > > Tahoe: http://tahoe.baselogic.com > > > > > > > > > > > > > > > > > > > > > -- > > > > Kent Närling > > > > > > > > System Architect > > > > SEAMLESS > > > > Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden > > > > Phone: +46 8 5648 7800, fax: +46 8 5648 7823 > > > > Mobile: +46 70 836 9925 > > > > Mail: [EMAIL PROTECTED] > > > > www.seamless.se > > > > > > > > > > > > > > > > -- > > > --- > > > Thank You… > > > > > > Mick Knutson > > > BASE Logic, inc. > > > > > > Website: http://baselogic.com > > > Blog: http://baselogic.com/blog > > > BLiNC Magazine: http://blincmagazine.com > > > Linked IN: http://linkedin.com/in/mickknutson > > > DJ Mi
Re: Advice how to structure a project I want to move to maven...
I always use multi-module, but I always am working on J2EE apps. If you want common shared projects, then split this up, but you still might have multi-modules if you are creating j2ee apps. On Thu, Jun 5, 2008 at 3:22 PM, Kent Närling <[EMAIL PROTECTED]> wrote: > 2008/6/6 Mick Knutson <[EMAIL PROTECTED]>: > > > dist is usually going to be an assembly, and you add assembly descriptors > > into src/assemble/*.xml > > You do not store the rpm's or bin's there. They do not end up in svn in > > other words. > > > > I have: > > root pom.xml > > |-->common 1..* jar's > > |-->core > > |-->src > > |-->assemble > > |-->main/resources > > |-->site > > |-->/xdoc/**.* (docs) > > |-->tools > > |-->webapps 1..* wars > > > > So common, core, tools, webapps etc would be modules of the main project? > So you all seem to recommend creating a module based layout? > > Maybe I expressed myself a bit unclear, I never meant that the dist > CONTAINED RPM:s or so! > I mean that it's CREATES RPM:s etc ;-) > > In a module based layout like this, what if I then want to work on a module > (ie a plugin etc) without having to checkout the main project? > Maybe I don't even have access to it? (only the jar:s) > > Also, what if we would like to release a separate version of a module > outside of a release? (ie a patch or a feature without having to do a > release cycle for the whole product) > I can only imagine that it will be a bit "messy" in SVN then? since the > modules won't have separate trunk:s and tag:s etc? or? > > > > > > On Thu, Jun 5, 2008 at 3:01 PM, Kent Närling <[EMAIL PROTECTED]> > > wrote: > > > > > Sorry, didn't get what you mean by that? > > > > > > You mean dist should not be a project on its own, or? > > > > > > > > > 2008/6/5 Mick Knutson <[EMAIL PROTECTED]>: > > > > > > > dist should be src/assemble for assemblies. > > > > > > > > On Thu, Jun 5, 2008 at 2:41 PM, Kent Närling < > [EMAIL PROTECTED] > > > > > > > wrote: > > > > > > > > > We have a project in SVN that is made of several projects, > something > > > like > > > > > this: > > > > > > > > > > - core - core project > > > > > - common - common libraries > > > > > - pluginA > > > > > - pluginB > > > > > ... etc > > > > > - doc - for documentation) > > > > > - tools - some command line tools > > > > > - dist - distribution project which packages all of the above > > projects > > > > into > > > > > one or more packages (RPM:s for instance) > > > > > > > > > > Most of the the projects generate jar:s, but some generate EAR:s. > > > > > > > > > > Now on one hand we could create a main project with modules, but > that > > > > ties > > > > > the modules so tightly to the main project, or? > > > > > And the plugins (and future plugins) we would like to be able to > give > > > to > > > > > third-party resources etc and they should not have access to most > > core > > > > > sources etc > > > > > Additionally, if we put modules in subdirectories in SVN (as > > > recommended) > > > > > it > > > > > becomes more awkward to release separate versions of the modules? > > > > > > > > > > At the end it should be easy to build the whole project and package > > it, > > > > for > > > > > instance automatically from within continuum for instance. > > > > > Additionally, for developers it should be easy to check out all > > > projects > > > > > automatically and recursively into Eclipse... > > > > > > > > > > Any suggestions about the best strategy for a project like this? > > > > > > > > > > //Kent > > > > > > > > > > > > > > > > > > > > > -- > > > > --- > > > > Thank You… > > > > > > > > Mick Knutson > > > > BASE Logic, inc. > > > > > > > > Website: http://baselogic.com > > > > Blog: http://baselogic.com/blog > > > > BLiNC Magazine: http://blincmagazine.com > > > > Linked IN: http://linkedin.com/in/mickknutson > > > > DJ Mick: http://djmick.com > > > > MySpace: http://myspace.com/mickknutson > > > > Tahoe: http://tahoe.baselogic.com > > > > > > > > > > > > > > > > -- > > > Kent Närling > > > > > > System Architect > > > SEAMLESS > > > Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden > > > Phone: +46 8 5648 7800, fax: +46 8 5648 7823 > > > Mobile: +46 70 836 9925 > > > Mail: [EMAIL PROTECTED] > > > www.seamless.se > > > > > > > > > > > -- > > --- > > Thank You… > > > > Mick Knutson > > BASE Logic, inc. > > > > Website: http://baselogic.com > > Blog: http://baselogic.com/blog > > BLiNC Magazine: http://blincmagazine.com > > Linked IN: http://linkedin.com/in/mickknutson > > DJ Mick: http://djmick.com > > MySpace: http://myspace.com/mickknutson > > Tahoe: http://tahoe.baselogic.com > > > > > > -- > Kent Närling > > System Architect > SEAMLESS > Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden > Phone: +46 8 5648 7800, fax: +46 8 5648 7823 > Mobile: +46 70 836 9925 > Mail: [EMAIL PROTECTED] > www.seamless.se > -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmaga
Re: Advice how to structure a project I want to move to maven...
2008/6/6 Mick Knutson <[EMAIL PROTECTED]>: > dist is usually going to be an assembly, and you add assembly descriptors > into src/assemble/*.xml > You do not store the rpm's or bin's there. They do not end up in svn in > other words. > > I have: > root pom.xml > |-->common 1..* jar's > |-->core > |-->src > |-->assemble > |-->main/resources > |-->site > |-->/xdoc/**.* (docs) > |-->tools > |-->webapps 1..* wars > So common, core, tools, webapps etc would be modules of the main project? So you all seem to recommend creating a module based layout? Maybe I expressed myself a bit unclear, I never meant that the dist CONTAINED RPM:s or so! I mean that it's CREATES RPM:s etc ;-) In a module based layout like this, what if I then want to work on a module (ie a plugin etc) without having to checkout the main project? Maybe I don't even have access to it? (only the jar:s) Also, what if we would like to release a separate version of a module outside of a release? (ie a patch or a feature without having to do a release cycle for the whole product) I can only imagine that it will be a bit "messy" in SVN then? since the modules won't have separate trunk:s and tag:s etc? or? > > On Thu, Jun 5, 2008 at 3:01 PM, Kent Närling <[EMAIL PROTECTED]> > wrote: > > > Sorry, didn't get what you mean by that? > > > > You mean dist should not be a project on its own, or? > > > > > > 2008/6/5 Mick Knutson <[EMAIL PROTECTED]>: > > > > > dist should be src/assemble for assemblies. > > > > > > On Thu, Jun 5, 2008 at 2:41 PM, Kent Närling <[EMAIL PROTECTED] > > > > > wrote: > > > > > > > We have a project in SVN that is made of several projects, something > > like > > > > this: > > > > > > > > - core - core project > > > > - common - common libraries > > > > - pluginA > > > > - pluginB > > > > ... etc > > > > - doc - for documentation) > > > > - tools - some command line tools > > > > - dist - distribution project which packages all of the above > projects > > > into > > > > one or more packages (RPM:s for instance) > > > > > > > > Most of the the projects generate jar:s, but some generate EAR:s. > > > > > > > > Now on one hand we could create a main project with modules, but that > > > ties > > > > the modules so tightly to the main project, or? > > > > And the plugins (and future plugins) we would like to be able to give > > to > > > > third-party resources etc and they should not have access to most > core > > > > sources etc > > > > Additionally, if we put modules in subdirectories in SVN (as > > recommended) > > > > it > > > > becomes more awkward to release separate versions of the modules? > > > > > > > > At the end it should be easy to build the whole project and package > it, > > > for > > > > instance automatically from within continuum for instance. > > > > Additionally, for developers it should be easy to check out all > > projects > > > > automatically and recursively into Eclipse... > > > > > > > > Any suggestions about the best strategy for a project like this? > > > > > > > > //Kent > > > > > > > > > > > > > > > > -- > > > --- > > > Thank You… > > > > > > Mick Knutson > > > BASE Logic, inc. > > > > > > Website: http://baselogic.com > > > Blog: http://baselogic.com/blog > > > BLiNC Magazine: http://blincmagazine.com > > > Linked IN: http://linkedin.com/in/mickknutson > > > DJ Mick: http://djmick.com > > > MySpace: http://myspace.com/mickknutson > > > Tahoe: http://tahoe.baselogic.com > > > > > > > > > > > -- > > Kent Närling > > > > System Architect > > SEAMLESS > > Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden > > Phone: +46 8 5648 7800, fax: +46 8 5648 7823 > > Mobile: +46 70 836 9925 > > Mail: [EMAIL PROTECTED] > > www.seamless.se > > > > > > -- > --- > Thank You… > > Mick Knutson > BASE Logic, inc. > > Website: http://baselogic.com > Blog: http://baselogic.com/blog > BLiNC Magazine: http://blincmagazine.com > Linked IN: http://linkedin.com/in/mickknutson > DJ Mick: http://djmick.com > MySpace: http://myspace.com/mickknutson > Tahoe: http://tahoe.baselogic.com > -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
Re: Advice how to structure a project I want to move to maven...
dist is usually going to be an assembly, and you add assembly descriptors into src/assemble/*.xml You do not store the rpm's or bin's there. They do not end up in svn in other words. I have: root pom.xml |-->common 1..* jar's |-->core |-->src |-->assemble |-->main/resources |-->site |-->/xdoc/**.* (docs) |-->tools |-->webapps 1..* wars On Thu, Jun 5, 2008 at 3:01 PM, Kent Närling <[EMAIL PROTECTED]> wrote: > Sorry, didn't get what you mean by that? > > You mean dist should not be a project on its own, or? > > > 2008/6/5 Mick Knutson <[EMAIL PROTECTED]>: > > > dist should be src/assemble for assemblies. > > > > On Thu, Jun 5, 2008 at 2:41 PM, Kent Närling <[EMAIL PROTECTED]> > > wrote: > > > > > We have a project in SVN that is made of several projects, something > like > > > this: > > > > > > - core - core project > > > - common - common libraries > > > - pluginA > > > - pluginB > > > ... etc > > > - doc - for documentation) > > > - tools - some command line tools > > > - dist - distribution project which packages all of the above projects > > into > > > one or more packages (RPM:s for instance) > > > > > > Most of the the projects generate jar:s, but some generate EAR:s. > > > > > > Now on one hand we could create a main project with modules, but that > > ties > > > the modules so tightly to the main project, or? > > > And the plugins (and future plugins) we would like to be able to give > to > > > third-party resources etc and they should not have access to most core > > > sources etc > > > Additionally, if we put modules in subdirectories in SVN (as > recommended) > > > it > > > becomes more awkward to release separate versions of the modules? > > > > > > At the end it should be easy to build the whole project and package it, > > for > > > instance automatically from within continuum for instance. > > > Additionally, for developers it should be easy to check out all > projects > > > automatically and recursively into Eclipse... > > > > > > Any suggestions about the best strategy for a project like this? > > > > > > //Kent > > > > > > > > > > > -- > > --- > > Thank You… > > > > Mick Knutson > > BASE Logic, inc. > > > > Website: http://baselogic.com > > Blog: http://baselogic.com/blog > > BLiNC Magazine: http://blincmagazine.com > > Linked IN: http://linkedin.com/in/mickknutson > > DJ Mick: http://djmick.com > > MySpace: http://myspace.com/mickknutson > > Tahoe: http://tahoe.baselogic.com > > > > > > -- > Kent Närling > > System Architect > SEAMLESS > Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden > Phone: +46 8 5648 7800, fax: +46 8 5648 7823 > Mobile: +46 70 836 9925 > Mail: [EMAIL PROTECTED] > www.seamless.se > -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com
Re: Advice how to structure a project I want to move to maven...
Sorry, didn't get what you mean by that? You mean dist should not be a project on its own, or? 2008/6/5 Mick Knutson <[EMAIL PROTECTED]>: > dist should be src/assemble for assemblies. > > On Thu, Jun 5, 2008 at 2:41 PM, Kent Närling <[EMAIL PROTECTED]> > wrote: > > > We have a project in SVN that is made of several projects, something like > > this: > > > > - core - core project > > - common - common libraries > > - pluginA > > - pluginB > > ... etc > > - doc - for documentation) > > - tools - some command line tools > > - dist - distribution project which packages all of the above projects > into > > one or more packages (RPM:s for instance) > > > > Most of the the projects generate jar:s, but some generate EAR:s. > > > > Now on one hand we could create a main project with modules, but that > ties > > the modules so tightly to the main project, or? > > And the plugins (and future plugins) we would like to be able to give to > > third-party resources etc and they should not have access to most core > > sources etc > > Additionally, if we put modules in subdirectories in SVN (as recommended) > > it > > becomes more awkward to release separate versions of the modules? > > > > At the end it should be easy to build the whole project and package it, > for > > instance automatically from within continuum for instance. > > Additionally, for developers it should be easy to check out all projects > > automatically and recursively into Eclipse... > > > > Any suggestions about the best strategy for a project like this? > > > > //Kent > > > > > > -- > --- > Thank You… > > Mick Knutson > BASE Logic, inc. > > Website: http://baselogic.com > Blog: http://baselogic.com/blog > BLiNC Magazine: http://blincmagazine.com > Linked IN: http://linkedin.com/in/mickknutson > DJ Mick: http://djmick.com > MySpace: http://myspace.com/mickknutson > Tahoe: http://tahoe.baselogic.com > -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
Re: Advice how to structure a project I want to move to maven...
dist should be src/assemble for assemblies. On Thu, Jun 5, 2008 at 2:41 PM, Kent Närling <[EMAIL PROTECTED]> wrote: > We have a project in SVN that is made of several projects, something like > this: > > - core - core project > - common - common libraries > - pluginA > - pluginB > ... etc > - doc - for documentation) > - tools - some command line tools > - dist - distribution project which packages all of the above projects into > one or more packages (RPM:s for instance) > > Most of the the projects generate jar:s, but some generate EAR:s. > > Now on one hand we could create a main project with modules, but that ties > the modules so tightly to the main project, or? > And the plugins (and future plugins) we would like to be able to give to > third-party resources etc and they should not have access to most core > sources etc > Additionally, if we put modules in subdirectories in SVN (as recommended) > it > becomes more awkward to release separate versions of the modules? > > At the end it should be easy to build the whole project and package it, for > instance automatically from within continuum for instance. > Additionally, for developers it should be easy to check out all projects > automatically and recursively into Eclipse... > > Any suggestions about the best strategy for a project like this? > > //Kent > -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com
Advice how to structure a project I want to move to maven...
We have a project in SVN that is made of several projects, something like this: - core - core project - common - common libraries - pluginA - pluginB ... etc - doc - for documentation) - tools - some command line tools - dist - distribution project which packages all of the above projects into one or more packages (RPM:s for instance) Most of the the projects generate jar:s, but some generate EAR:s. Now on one hand we could create a main project with modules, but that ties the modules so tightly to the main project, or? And the plugins (and future plugins) we would like to be able to give to third-party resources etc and they should not have access to most core sources etc Additionally, if we put modules in subdirectories in SVN (as recommended) it becomes more awkward to release separate versions of the modules? At the end it should be easy to build the whole project and package it, for instance automatically from within continuum for instance. Additionally, for developers it should be easy to check out all projects automatically and recursively into Eclipse... Any suggestions about the best strategy for a project like this? //Kent
Re: Trouble with import scope
> So in our case we are trying to manage the Websphere runtime classpath > as a single set of dependencies. The case for doing this is pretty > strong and we've been using it to aggregate the container library into a > single dependency in our projects for while. I was hoping the import > scope would make this a first class pattern and relieve my future > proofing concern with it. Tim, I totally get where you're coming from, and I understand why you might be a little bit confused about the import scope. I agree that your use case makes a lot of sense and would help management of artifact bundles across projects -- perhaps it can be incorporated into this "import" scope at some time in the future. Unless of course the current way works with no issues -- as you said, you are already doing it. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Trouble with import scope
Hi Simon,
I'm aware of the difference btw dependencies and dependencyManagement.
When I first heard about the feature proposal I thought it was to inline
dependencies into poms. My line of thinking was of course into the
dependencies section.
When I read that you put that scope only in the dependency management
section it just didn't make occur to me (I thought, well maybe the
dependency resolver needs it there for some ordering issue or just
that's odd) I never made the leap to think it was actually not for
{depenendencies}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Trouble with import scope
> Wayne Fay wrote: > > The real use case for import scope IMO is where a company > does not want to use a single shared corporate parent pom, > but they do want to enforce versions on all projects. So you > manage versions in the imported pom (one place), force all > your projects to import it (can be any pom in the repo), and > poof they all get version maintenance for free. > Hi Wayne, Hmmm, if that's true I did misunderstand the intent. I thought it was to handle the 'dependency aggregator pattern' as a scope instead of perhaps mis-using transitive dependencies. I'm using the term 'dependency aggregator', others on the ML's have called it different things. (inheritance pom or meta pom have been used I think) So in our case we are trying to manage the Websphere runtime classpath as a single set of dependencies. The case for doing this is pretty strong and we've been using it to aggregate the container library into a single dependency in our projects for while. I was hoping the import scope would make this a first class pattern and relieve my future proofing concern with it. What you say would explain..it didn't make sense to me that it went into dependencyManagement. Best regards -TR - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trouble with import scope
On Thu, 2008-06-05 at 15:32 -0500, Wayne Fay wrote: > I haven't used it yet myself, but from my reading of the > documentation, I believe it really only brings in the > dependencyManagement section of the imported pom. So you will still > need to declare struts-core in the project you need to use it, but you > can leave off the version (and scope). > > The real use case for import scope IMO is where a company does not > want to use a single shared corporate parent pom, but they do want to > enforce versions on all projects. So you manage versions in the > imported pom (one place), force all your projects to import it (can be > any pom in the repo), and poof they all get version maintenance for > free. Except that it doesn't "force" lib versions at all. It just provides defaults for when a pom doesn't explicitly set them itself. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trouble with import scope
On Thu, 2008-06-05 at 15:41 -0400, Timothy Reilly wrote: > I don't think I'm understanding the docs here regarding how to use > import scope: > http://maven.apache.org/guides/introduction/introduction-to-dependency-m > echanism.html#Importing_Dependencies > > Here is what I have - must be incorrect I think... > > parent >+ testapp >+ testimports (not a module) > > > parent pom: > > > http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > 4.0.0 > com.test > parent > pom > parent > 0.0.1-SNAPSHOT > > > > testapp > > > > > Testimports pom: > > > 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";> > > 4.0.0 > com.test.imports > testimports > pom > testimports > 0.0.1-SNAPSHOT > > > > > org.apache.struts > struts-core > 1.3.9 > provided > > > > > > > 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";> > > parent > com.test > 0.0.1-SNAPSHOT > > 4.0.0 > com.test.app > testapp > jar > testapp > 0.0.1-SNAPSHOT > > > > > > com.test.imports > testimports > pom > 0.0.1-SNAPSHOT > import > > > > > > === > Maven version: 2.0.9 > Java version: 1.5.0 > OS name: "windows xp" version: "5.1 build 2600 service pack 2" arch: > "x86" Family: "dos" > = > What are you expecting to happen? I wasn't aware of the new "import" scope, but it seems from reading the page that it imports *dependencyManagement* data, not dependencies. And your com.test:parent doesn't declare any dependencies at all, so it doesn't use any dependencyManagement data at all. Are you sure you know the difference between dependency and dependencyManagement? If not, then I suggest re-reading the page that you linked to. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trouble with import scope
I haven't used it yet myself, but from my reading of the documentation, I believe it really only brings in the dependencyManagement section of the imported pom. So you will still need to declare struts-core in the project you need to use it, but you can leave off the version (and scope). The real use case for import scope IMO is where a company does not want to use a single shared corporate parent pom, but they do want to enforce versions on all projects. So you manage versions in the imported pom (one place), force all your projects to import it (can be any pom in the repo), and poof they all get version maintenance for free. Wayne On Thu, Jun 5, 2008 at 2:41 PM, Timothy Reilly <[EMAIL PROTECTED]> wrote: > > I don't think I'm understanding the docs here regarding how to use > import scope: > http://maven.apache.org/guides/introduction/introduction-to-dependency-m > echanism.html#Importing_Dependencies > > Here is what I have - must be incorrect I think... > > parent > + testapp > + testimports (not a module) > > > parent pom: > > > http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd"; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > 4.0.0 > com.test > parent > pom > parent > 0.0.1-SNAPSHOT > > > >testapp > > > > > Testimports pom: > > > 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";> > >4.0.0 >com.test.imports >testimports >pom >testimports >0.0.1-SNAPSHOT > > > > >org.apache.struts >struts-core >1.3.9 >provided > > > > > > > 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";> > >parent >com.test >0.0.1-SNAPSHOT > >4.0.0 >com.test.app >testapp >jar >testapp >0.0.1-SNAPSHOT > > > > > >com.test.imports >testimports >pom >0.0.1-SNAPSHOT >import > > > > > > === > Maven version: 2.0.9 > Java version: 1.5.0 > OS name: "windows xp" version: "5.1 build 2600 service pack 2" arch: > "x86" Family: "dos" > = > > Any advice appreciated. > > - > 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]
ARchetype
I'm having trouble getting the archetype plugin to update. I deleted all the versions in my personal repository. But when I run "mvn archetype:generate" it downloads version 1.0-aplha-4 instead of the latest version 2.0-alpha-3. Looking at the meta data at http://repo1.maven.org/maven2/org/apache/maven/archetype/maven-archetype/maven-metadata.xml : org.apache.maven.archetype maven-archetype 1.0-alpha-4 2.0-alpha-3 1.0-alpha-4 1.0-alpha-7 2.0-alpha-1 2.0-alpha-2 2.0-alpha-3 20080424212921 Is the version in the tag the default? Should it be changed? -- Esse Quam Videre To Be, rather than to Seem
Trouble with import scope
I don't think I'm understanding the docs here regarding how to use import scope: http://maven.apache.org/guides/introduction/introduction-to-dependency-m echanism.html#Importing_Dependencies Here is what I have - must be incorrect I think... parent + testapp + testimports (not a module) parent pom: http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> 4.0.0 com.test parent pom parent 0.0.1-SNAPSHOT testapp Testimports pom: 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";> 4.0.0 com.test.imports testimports pom testimports 0.0.1-SNAPSHOT org.apache.struts struts-core 1.3.9 provided 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";> parent com.test 0.0.1-SNAPSHOT 4.0.0 com.test.app testapp jar testapp 0.0.1-SNAPSHOT com.test.imports testimports pom 0.0.1-SNAPSHOT import === Maven version: 2.0.9 Java version: 1.5.0 OS name: "windows xp" version: "5.1 build 2600 service pack 2" arch: "x86" Family: "dos" = Any advice appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Calling ant tasks from maven pom
Tim i indeed wht u suggested but the build xmls just dont seem to to reached.. On Thu, Jun 5, 2008 at 6:53 PM, Tim Kettler <[EMAIL PROTECTED]> wrote: > > Hi, (again :-) ) > > Niranjan Deshpande schrieb: > > I am trying to execute ant tasks from maven's pom as below. >> >> >> >> >> maven-antrun-plugin >> >> 1.1 >> >> >> >> >> >> generate-sources >> >> >> >> >> >> > >> failonerror="true"> >> >> >> >> >> >> >> >> >> >> run >> >> >> >> >> >> >> >> >> The generate.sh file has 10 xml files that i want to run as >> ant -buildfile -filename >> >> for the time being I am running the plugin as maven antrun:run, just to >> find >> whether the .sh file is called or not. But i am geting this: >> [INFO] [antrun:run] >> [INFO] Executing tasks >> [INFO] Executed tasks >> >> I have added a ECHO in the .sh file, but i see none at the output >> >> > First to answer your concrete problem: When you call a plugin goal directly > from the commandline it uses the common configuration under > as there may be more than one execution defined > and there is no sane way to decide which ones configuration to use. > > Secondly, just to recap that I understood correctly what you are doing: > > You have a maven build from which you want to call a shell script which in > turn triggers a few ant builds?!? > > Cant you just configure multiple calls of the task [1] in your > antrun-plugin configuration and throw away the shell script completely? > > -Tim > > [1] http://ant.apache.org/manual/CoreTasks/ant.html > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Regards, Niranjan Deshpande "Shut yourself from the world and create the reality you want"
Re: [m2] how can I set a jndi datasource inside embedded tomcat with cargo?
On Thu, Jun 5, 2008 at 2:37 PM, Mick Knutson <[EMAIL PROTECTED]> wrote: > how can I set a jndi datasource inside embedded tomcat with cargo? > There isn't really good documentation on this subject that I'm aware of. Here's an example, though: http://blogs.atlassian.com/developer/2007/03/from_manual_to_automatic.html Just search for cargo.datasource. - Geoffrey -- Geoffrey Wiseman
Re: WEB-INF/classes/META-INF
Thanks (and sorry for submitting this request to the wrong group earlier). If I wasn't clear, I do need the result to be: -- target |-- classes `-- AppServices |-- META-INF | `-- services | `-- org.apache.commons.logging.LogFactory `-- WEB-INF `-- classes Not -- target |-- classes `-- AppServices |-- META-INF `-- WEB-INF |-- classes `-- META-INF `-- services `-- org.apache.commons.logging.LogFactory Anyhow, you're right. That did work. I moved the META-INF directory under webapp to be a sibling of WEB-INF. It's building as expected. AppServices |-- pom.xml `-- src `-- main |-- java |-- resources `-- webapp |-- WEB-INF `-- META-INF `-- services `-- org.apache.commons.logging.LogFactory I think our confusion was that this is a different practice than for a JAR project and we wanted to stay 'true' to the Maven directory structure. For a JAR (Java project), the custom META-INF does go under the resources directly and builds just fine. Thanks again! "Brett Porter" <[EMAIL PROTECTED]> 06/05/2008 01:05 PM Please respond to "Maven Users List" To "Maven Users List" cc Subject Re: WEB-INF/classes/META-INF This isn't a bug - resources is "class path" resources in the context of Java, which happens to be in WEB-INF/classes for a web app, and / for a JAR. You have two options: - add the files directly to src/main/webapp - use the war plugin's webResources configuration to add a new location (this is assuming that this is what works, I'm not familiar if META-INF/services is read from the root of a webapp or not) - Brett 2008/6/6 Jerry Thome <[EMAIL PROTECTED]>: > I need to add a "META-INF/services/org.apache.commons.logging.LogFactory" > to tell commons-logging to use log4j (a pretty basic thing I think). I > thought I was suppose to add it to the main/resources/ directory. As many > of you know, it copies everything from here to the WEB-INF/classes > directory. > > AppServices > |-- pom.xml > |-- src > ||-- main > || |-- java > || |-- resources > || | `-- META-INF > || | `-- services > || | `-- org.apache.commons.logging.LogFactory > || `-- webapp > || > |`-- test > |`-- java > |`-- ... > `-- target >|-- classes >`-- AppServices >|-- META-INF >`-- WEB-INF >`-- classes >`-- META-INF >`-- services >`-- org.apache.commons.logging.LogFactory > > Is this a bug? Am I putting the "META-INF/services" in the wrong place? I > am currently using Maven 2.0.9. > > > > Thank you! > > > > The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail. > > > -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-ma
[m2] how can I set a jndi datasource inside embedded tomcat with cargo?
how can I set a jndi datasource inside embedded tomcat with cargo? -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com
Re: Control pom Inheritance
>Not uncommon for people to solve this problem by putting together a 'parent' >POM that contains only those inheritable bits, and subbing that for all >actual projects. hm... but that only works if one is in control of all the participating poms. I'd like to use a given pom as parent pom. mf -- View this message in context: http://www.nabble.com/Control-pom-Inheritance-tp17673855p17676737.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WEB-INF/classes/META-INF
This isn't a bug - resources is "class path" resources in the context of Java, which happens to be in WEB-INF/classes for a web app, and / for a JAR. You have two options: - add the files directly to src/main/webapp - use the war plugin's webResources configuration to add a new location (this is assuming that this is what works, I'm not familiar if META-INF/services is read from the root of a webapp or not) - Brett 2008/6/6 Jerry Thome <[EMAIL PROTECTED]>: > I need to add a "META-INF/services/org.apache.commons.logging.LogFactory" > to tell commons-logging to use log4j (a pretty basic thing I think). I > thought I was suppose to add it to the main/resources/ directory. As many > of you know, it copies everything from here to the WEB-INF/classes > directory. > > AppServices > |-- pom.xml > |-- src > ||-- main > || |-- java > || |-- resources > || | `-- META-INF > || | `-- services > || | `-- org.apache.commons.logging.LogFactory > || `-- webapp > || > |`-- test > |`-- java > |`-- ... > `-- target >|-- classes >`-- AppServices >|-- META-INF >`-- WEB-INF >`-- classes >`-- META-INF >`-- services >`-- org.apache.commons.logging.LogFactory > > Is this a bug? Am I putting the "META-INF/services" in the wrong place? I > am currently using Maven 2.0.9. > > > > Thank you! > > > > The information contained in this e-mail and any accompanying documents may > contain information that is confidential or otherwise protected from > disclosure. If you are not the intended recipient of this message, or if this > message has been addressed to you in error, please immediately alert the > sender by reply e-mail and then delete this message, including any > attachments. Any dissemination, distribution or other use of the contents of > this message by anyone other than the intended recipient is strictly > prohibited. All messages sent to and from this e-mail address may be > monitored as permitted by applicable law and regulations to ensure compliance > with our internal policies and to protect our business. E-mails are not > secure and cannot be guaranteed to be error free as they can be intercepted, > amended, lost or destroyed, or contain viruses. You are deemed to have > accepted these risks if you communicate with us by e-mail. > > > -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Control pom Inheritance
On Thu, Jun 5, 2008 at 12:15 PM, martinf <[EMAIL PROTECTED]> wrote: > > Hi all, > > is it possible to control which elements a pom inherits from its parent > pom? > > Like is there a way to inherit all elements form the > but inherit no element beyond parents pom element? > > Well, and if its possible, how can it be done? > Not uncommon for people to solve this problem by putting together a 'parent' POM that contains only those inheritable bits, and subbing that for all actual projects. - Geoffrey -- Geoffrey Wiseman
WEB-INF/classes/META-INF
I need to add a "META-INF/services/org.apache.commons.logging.LogFactory" to tell commons-logging to use log4j (a pretty basic thing I think). I thought I was suppose to add it to the main/resources/ directory. As many of you know, it copies everything from here to the WEB-INF/classes directory. AppServices |-- pom.xml |-- src ||-- main || |-- java || |-- resources || | `-- META-INF || | `-- services || | `-- org.apache.commons.logging.LogFactory || `-- webapp || |`-- test |`-- java |`-- ... `-- target |-- classes `-- AppServices |-- META-INF `-- WEB-INF `-- classes `-- META-INF `-- services `-- org.apache.commons.logging.LogFactory Is this a bug? Am I putting the "META-INF/services" in the wrong place? I am currently using Maven 2.0.9. Thank you! The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: Error deploying to a remote respository using scm
So I get this again: *The authenticity of host '208.96.48.200' can't be established. RSA key fingerprint is 15:6f:d1:60:05:21:dd:43:4b:4d:d6:9e:4f:3b:aa:e4. Are you sure you want to continue connecting? (yes/no): y* And I do NOT see anything in my security logs: Jun 5 08:07:13 12825-42150 sshd[9696]: subsystem request for sftp Jun 5 09:37:29 12825-42150 sshd[3279]: pam_unix(sshd:session): session closed for user root Jun 5 09:37:31 12825-42150 sshd[2493]: pam_unix(sshd:session): session closed for user root Jun 5 09:37:31 12825-42150 sshd[2429]: pam_unix(sshd:session): session closed for user root As this request I just made was at 10:14 and the access above was for root, not admin anyways. On Thu, Jun 5, 2008 at 7:10 AM, Krishnamurthi, Venkat < [EMAIL PROTECTED]> wrote: > This is the output of ssh2 -V: > > ssh2: SSH Tectia Server 4.4.8 on i686-pc-linux-gnu > Build: 21 > Crypto library version: SSH Cryptographic Library, version 1.2.6 > FIPS certification mode: DISABLED > Product: SSH Tectia Server (A) > License type: commercial > > Thanks, > Venkat > > -Original Message- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 04, 2008 7:36 PM > To: Maven Users List > Subject: Re: Error deploying to a remote respository using scm > > The stack trace says very clearly: > Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed to > authenticate. (or you have too old ssh2 installed, check with ssh2 -V) > > So, what does "ssh2 -V" say? > > Wayne > > On Wed, Jun 4, 2008 at 5:12 PM, Krishnamurthi, Venkat > <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I'm trying to deploy a snapshot jar to a remote repository. I followed > > > the instructions given here: > > > > http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-ss > > h- > > external.html > > > > However, when I execute mvn deploy, I get the following error: > > > > [INFO] [deploy:deploy] > > [INFO] Retrieving previous build number from scp_snapshot [WARNING] > > repository metadata for: 'snapshot demo:demo:1.0-SNAPSHOT' > > could not be retrieved from repository: scp_snapshot due to an error: > > Exit code: 78 - warning: Authentication failed. > > Disconnected (local); connection lost (Connection closed by remote > > host.). > > Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed > > to authenticate. (or you have too old ssh2 installed, check with ssh2 > > -V) > > > > [INFO] Repository 'scp_snapshot' will be blacklisted > > Uploading: > > scpexe://eqp2fcc:1080/scp_snapshot/demo/demo/1.0-SNAPSHOT/demo-1.0-SNA > > PS > > HOT.jar > > [INFO] > > -- > > -- > > [ERROR] BUILD ERROR > > [INFO] > > -- > > -- [INFO] Error deploying artifact: Error executing command for > > transfer > > > > Exit code 74 - warning: Authentication failed. > > Disconnected (local); connection lost (Connection closed by remote > > host.). > > Disconnect reason 10, exit code = 74 > > > > My pom.xml has the following distributionManagement: > > > > > > > > > > false > > scp_snapshot > > SCP Snapshot Repository > > scpexe://eqp2fcc:1080/scp_snapshot > > default > > > > > > > > Also, I added the following to my settings.xml > > > > > > > > scp_snapshot > > my_username > > my_password > > > > > > > > Please help me resolve this issue. > > > > > > Thanks, > > Venkat > > > > - > > 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] > > -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com
Re: Calling ant tasks from maven pom
Hi, (again :-) ) Niranjan Deshpande schrieb: I am trying to execute ant tasks from maven's pom as below. maven-antrun-plugin 1.1 generate-sources run The generate.sh file has 10 xml files that i want to run as ant -buildfile -filename for the time being I am running the plugin as maven antrun:run, just to find whether the .sh file is called or not. But i am geting this: [INFO] [antrun:run] [INFO] Executing tasks [INFO] Executed tasks I have added a ECHO in the .sh file, but i see none at the output First to answer your concrete problem: When you call a plugin goal directly from the commandline it uses the common configuration under as there may be more than one execution defined and there is no sane way to decide which ones configuration to use. Secondly, just to recap that I understood correctly what you are doing: You have a maven build from which you want to call a shell script which in turn triggers a few ant builds?!? Cant you just configure multiple calls of the task [1] in your antrun-plugin configuration and throw away the shell script completely? -Tim [1] http://ant.apache.org/manual/CoreTasks/ant.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Error getting reports from the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin'
Yes, but I do not see a described resolution. On Thu, Jun 5, 2008 at 9:34 AM, Tim Kettler <[EMAIL PROTECTED]> wrote: > Hi, > > Mick Knutson schrieb: > >> I have the following for my reports declaration: >> ... >> >> Then I noticed Checkstyle 2.2 got downloaded this morning on my build (mvn >> site actually), but then I got this failure: >> > > [...] > > Could this be related to this [1] recent discussion on the dev list. I > haven't followed the discussion closely, but skimming through your log it's > about the same topic: site plugin, project-info-report and snapshots > > -Tim > > [1] > http://www.nabble.com/Multiple-concurrent-SNAPSHOTs-for-MSITE-and-MPIR-isn%27t-working-to17607858.html > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com
Re: download maven-antrun-plugin
done :) On 6/5/08, Tim Kettler <[EMAIL PROTECTED]> wrote: > > Hi, > > Niranjan Deshpande schrieb: > >> please give me the link from where I can download this plugin. >> >> > You don't need to download a plugin in maven 2 manually, just configure it > in your POM and maven will take care of downloading it to your local > repository during execution. > > On the plugin homepage [1] you can find instructions on how to configure it > in your POM. > > -Tim > > [1] http://maven.apache.org/plugins/maven-antrun-plugin/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Regards, Niranjan Deshpande "Shut yourself from the world and create the reality you want"
Re: [m2] Error getting reports from the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin'
Hi, Mick Knutson schrieb: I have the following for my reports declaration: ... Then I noticed Checkstyle 2.2 got downloaded this morning on my build (mvn site actually), but then I got this failure: [...] Could this be related to this [1] recent discussion on the dev list. I haven't followed the discussion closely, but skimming through your log it's about the same topic: site plugin, project-info-report and snapshots -Tim [1] http://www.nabble.com/Multiple-concurrent-SNAPSHOTs-for-MSITE-and-MPIR-isn%27t-working-to17607858.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Calling ant tasks from maven pom
I am trying to execute ant tasks from maven's pom as below. maven-antrun-plugin 1.1 generate-sources run The generate.sh file has 10 xml files that i want to run as ant -buildfile -filename for the time being I am running the plugin as maven antrun:run, just to find whether the .sh file is called or not. But i am geting this: [INFO] [antrun:run] [INFO] Executing tasks [INFO] Executed tasks I have added a ECHO in the .sh file, but i see none at the output
Re: Control pom Inheritance
martinf schrieb: > Hi all, > > is it possible to control which elements a pom inherits from its parent pom? > > Like is there a way to inherit all elements form the > but inherit no element beyond parents pom element? > No. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: download maven-antrun-plugin
Hi, Niranjan Deshpande schrieb: please give me the link from where I can download this plugin. You don't need to download a plugin in maven 2 manually, just configure it in your POM and maven will take care of downloading it to your local repository during execution. On the plugin homepage [1] you can find instructions on how to configure it in your POM. -Tim [1] http://maven.apache.org/plugins/maven-antrun-plugin/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Control pom Inheritance
Hi all, is it possible to control which elements a pom inherits from its parent pom? Like is there a way to inherit all elements form the but inherit no element beyond parents pom element? Well, and if its possible, how can it be done? Martin -- View this message in context: http://www.nabble.com/Control-pom-Inheritance-tp17673855p17673855.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Error getting reports from the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin'
I have the following for my reports declaration: ... Then I noticed Checkstyle 2.2 got downloaded this morning on my build (mvn site actually), but then I got this failure: this realm = plexus.core urls[0] = file:/C:/apache-maven-2.0.8/bin/../lib/maven-2.0.8-uber.jar urls[1] = file:/c:/opt/.m2/repository/org/apache/maven/wagon/wagon-ssh-common/1.0-beta-2/wagon-ssh-common-1.0-beta-2.jar urls[2] = file:/c:/opt/.m2/repository/com/baselogic/qa-tools/3.0-SNAPSHOT/qa-tools-3.0-SNAPSHOT.jar urls[3] = file:/c:/opt/.m2/repository/mysql/mysql-connector-java/5.1.6/mysql-connector-java-5.1.6.jar Number of imports: 6 import: [EMAIL PROTECTED] import: [EMAIL PROTECTED] import: [EMAIL PROTECTED] import: [EMAIL PROTECTED] import: [EMAIL PROTECTED] import: [EMAIL PROTECTED] - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error getting reports from the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin': Unable to find the mojo 'org.apache.ma ven.plugins:maven-project-info-reports-plugin:2.2-SNAPSHOT:summary' in the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' org/apache/maven/doxia/logging/Log [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error getting reports from the plugin 'org.apache.maven.plugins:maven-project-info-report s-plugin': Unable to find the mojo 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.2-SNAPSHOT:summary' in the plugin 'org.apache.ma ven.plugins:maven-project-info-reports-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:642) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:517) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) 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) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.apache.maven.plugins:maven-project-info-reports-plugin:2. 2-SNAPSHOT:summary' in the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:575) at org.apache.maven.plugin.DefaultPluginManager.getReport(DefaultPluginManager.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:683) ... 18 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.plugin.Mojoo rg.apache.maven.plugins:maven-project-info-reports-plugin:2.2-SNAPSHOT:summary', it could not be started at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:339) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:566) ... 20 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error starting component at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:109) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractCompone
download maven-antrun-plugin
please give me the link from where I can download this plugin. -- Regards, Niranjan Deshpande "Shut yourself from the world and create the reality you want"
Re: How to execute a script in maven2 ?
This shows how to execute a script file in a maven phase using Ant scripting. See the sample. http://maven.apache.org/guides/mini/guide-using-ant.html Upul On Thu, Jun 5, 2008 at 7:50 PM, nicolas.duminil < [EMAIL PROTECTED]> wrote: > > Greetings, > > I need to execute a script (bat, cmd, sh, etc.) in maven and I don't find > anything. I can execute a Java app but don't know how to launch a .bat > file. > Please help. > > Kind regards, > > Nicolas > -- > View this message in context: > http://www.nabble.com/How-to-execute-a-script-in-maven2---tp17670955p17670955.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: How to execute a script in maven2 ?
Nicolas; Am Thu, 5 Jun 2008 07:20:04 -0700 (PDT) schrieb "nicolas.duminil" <[EMAIL PROTECTED]>: > I need to execute a script (bat, cmd, sh, etc.) in maven and I don't > find anything. I can execute a Java app but don't know how to launch > a .bat file. Please help. I am doing things like that using exec:exec plugin which should allow for executing arbitrary system executables from within maven. Haven't tried using .bat files with that, though, but am pretty sure at least .sh (Unix) works... http://mojo.codehaus.org/exec-maven-plugin/exec-mojo.html http://mojo.codehaus.org/exec-maven-plugin/usage.html Cheers, Kristian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to execute a script in maven2 ?
Greetings, I need to execute a script (bat, cmd, sh, etc.) in maven and I don't find anything. I can execute a Java app but don't know how to launch a .bat file. Please help. Kind regards, Nicolas -- View this message in context: http://www.nabble.com/How-to-execute-a-script-in-maven2---tp17670955p17670955.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Error deploying to a remote respository using scm
This is the output of ssh2 -V: ssh2: SSH Tectia Server 4.4.8 on i686-pc-linux-gnu Build: 21 Crypto library version: SSH Cryptographic Library, version 1.2.6 FIPS certification mode: DISABLED Product: SSH Tectia Server (A) License type: commercial Thanks, Venkat -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 04, 2008 7:36 PM To: Maven Users List Subject: Re: Error deploying to a remote respository using scm The stack trace says very clearly: Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed to authenticate. (or you have too old ssh2 installed, check with ssh2 -V) So, what does "ssh2 -V" say? Wayne On Wed, Jun 4, 2008 at 5:12 PM, Krishnamurthi, Venkat <[EMAIL PROTECTED]> wrote: > Hi, > > I'm trying to deploy a snapshot jar to a remote repository. I followed > the instructions given here: > > http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-ss > h- > external.html > > However, when I execute mvn deploy, I get the following error: > > [INFO] [deploy:deploy] > [INFO] Retrieving previous build number from scp_snapshot [WARNING] > repository metadata for: 'snapshot demo:demo:1.0-SNAPSHOT' > could not be retrieved from repository: scp_snapshot due to an error: > Exit code: 78 - warning: Authentication failed. > Disconnected (local); connection lost (Connection closed by remote > host.). > Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed > to authenticate. (or you have too old ssh2 installed, check with ssh2 > -V) > > [INFO] Repository 'scp_snapshot' will be blacklisted > Uploading: > scpexe://eqp2fcc:1080/scp_snapshot/demo/demo/1.0-SNAPSHOT/demo-1.0-SNA > PS > HOT.jar > [INFO] > -- > -- > [ERROR] BUILD ERROR > [INFO] > -- > -- [INFO] Error deploying artifact: Error executing command for > transfer > > Exit code 74 - warning: Authentication failed. > Disconnected (local); connection lost (Connection closed by remote > host.). > Disconnect reason 10, exit code = 74 > > My pom.xml has the following distributionManagement: > > > > > false > scp_snapshot > SCP Snapshot Repository > scpexe://eqp2fcc:1080/scp_snapshot > default > > > > Also, I added the following to my settings.xml > > > > scp_snapshot > my_username > my_password > > > > Please help me resolve this issue. > > > Thanks, > Venkat > > - > 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: Error deploying to a remote respository using scm
There was an issue with my server path in the last case (I included port
no.). Now I removed the port number and gave the path from root. Now, I
get the following error:
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from scp_inhouse_snapshot
[WARNING] repository metadata for: 'snapshot demo:demo:1.0-SNAPSHOT'
could not be retrieved from repository: scp_snapshot due to an error:
Exit code: 78 -
You are authorized to use this System for approved business purposes
only.
Use for any other purpose is prohibited. All transactional records,
reports,
e-mail, software, and other data generated by or residing upon this
System
are the property of the Company and may be used by the Company for any
purpose.
Authorized and unauthorized activities may be monitored.
Keyboard-interactive:
PAM authentication
Keyboard-interactive:
PAM authentication
Keyboard-interactive:
PAM authentication
warning: Authentication failed.
Disconnected (local); no more authentication methods available (No
further authentication methods available.).
Disconnect reason 14, exit code = 78scp: warning: ssh2 client failed to
authenticate. (or you have too old ssh2 installed, check with ssh2 -V)
[INFO] Repository 'scp_snapshot' will be blacklisted
Uploading:
scpexe://eqz2pff:/demo/maven2_repositories/scp_snapshot/demo/demo/1.0-SN
APSHOT/demo-1.0-SNAPSHOT.jar
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error deploying artifact: Error executing command for transfer
Exit code 78 -
You are authorized to use this System for approved business purposes
only.
Use for any other purpose is prohibited. All transactional records,
reports,
e-mail, software, and other data generated by or residing upon this
System
are the property of the Company and may be used by the Company for any
purpose.
Authorized and unauthorized activities may be monitored.
Keyboard-interactive:
PAM authentication
Keyboard-interactive:
PAM authentication
Keyboard-interactive:
PAM authentication
warning: Authentication failed.
Disconnected (local); no more authentication methods available (No
further authentication methods available.).
Disconnect reason 14, exit code = 78
Thanks for your help.
Best Regards,
Venkat
-Original Message-
From: Mick Knutson [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2008 9:56 AM
To: Maven Users List
Subject: Re: Error deploying to a remote respository using scm
In additional to that, I am trying any way I can to deploy site docs:
I keep getting this error:
*[INFO] [site:deploy]
The authenticity of host '208.96.48.200' can't be established.
RSA key fingerprint is 15:6f:d1:60:05:21:dd:43:4b:4d:d6:9e:4f:3b:aa:e4.
Are you sure you wan*t to continue connecting? (yes/no):
I have create a ppk and key from putty, and have added this to my
pom.xml
site.internal
site.internal
${siteUrl}
And here is my settings.xml
site.internal
[username]
[password]
664
755
c:/ssh/internal-private.ppk
plink
pscp
...
scp://208.0.50.1/:/var/www/html/site
I have spent all day on this, and can't find anything that fixes this
issue.
On Thu, Jun 5, 2008 at 6:49 AM, Krishnamurthi, Venkat <
[EMAIL PROTECTED]> wrote:
> Hi,
>
> I get the same error when I execute ssh2 -V on my windows XP machine:
>
> C:\ssh2 -V
> 'ssh2' is not recognized as an internal or external command, operable
> program or batch file.
>
> Please help me resolve this.
>
> Thanks,
> Venkat
>
> -Original Message-
> From: Mick Knutson [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 04, 2008 7:40 PM
> To: Maven Users List
> Subject: Re: Error deploying to a remote respository using scm
>
> on XP, I use that command adn get:
>
> *C:\opt\baselogic>ssh2 -V
> 'ssh2' is not recognized as an internal or external command, operable
> program or batch file.
>
> C:\opt\baselogic>ssh -V
> 'ssh' is not recognized as an internal or external command, operable
> program or batch file.
>
> C:\opt\baselogic>
> *
>
> Then when I try to deploy with scpexe it does the same thing.
>
>
>
> On Wed, Jun 4, 2008 at 4:36 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
>
> > The stack trace says very clearly:
> > Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed
> > to authenticate. (or you have too old ssh2 installed, check with
> > ssh2
> > -V)
> >
> > So, what does "ssh2 -V" say?
> >
> > Wayne
> >
> > On Wed, Jun 4, 2008 at 5:12 PM, Krishnamurthi, Venkat
> > <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > I'm trying to deploy a snapshot jar to a remote repository. I
> > > followed the instructions given here:
> > >
> > > http://maven.apache.org/plugins/maven-deploy-plugin/examples/deplo
> > > y-
> > > ssh-
> > > ext
Re: Error deploying to a remote respository using scm
In additional to that, I am trying any way I can to deploy site docs:
I keep getting this error:
*[INFO] [site:deploy]
The authenticity of host '208.96.48.200' can't be established.
RSA key fingerprint is 15:6f:d1:60:05:21:dd:43:4b:4d:d6:9e:4f:3b:aa:e4.
Are you sure you wan*t to continue connecting? (yes/no):
I have create a ppk and key from putty, and have added this to my pom.xml
site.internal
site.internal
${siteUrl}
And here is my settings.xml
site.internal
[username]
[password]
664
755
c:/ssh/internal-private.ppk
plink
pscp
...
scp://208.0.50.1/:/var/www/html/site
I have spent all day on this, and can't find anything that fixes this issue.
On Thu, Jun 5, 2008 at 6:49 AM, Krishnamurthi, Venkat <
[EMAIL PROTECTED]> wrote:
> Hi,
>
> I get the same error when I execute ssh2 -V on my windows XP machine:
>
> C:\ssh2 -V
> 'ssh2' is not recognized as an internal or external command,
> operable program or batch file.
>
> Please help me resolve this.
>
> Thanks,
> Venkat
>
> -Original Message-
> From: Mick Knutson [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 04, 2008 7:40 PM
> To: Maven Users List
> Subject: Re: Error deploying to a remote respository using scm
>
> on XP, I use that command adn get:
>
> *C:\opt\baselogic>ssh2 -V
> 'ssh2' is not recognized as an internal or external command, operable
> program or batch file.
>
> C:\opt\baselogic>ssh -V
> 'ssh' is not recognized as an internal or external command, operable
> program or batch file.
>
> C:\opt\baselogic>
> *
>
> Then when I try to deploy with scpexe it does the same thing.
>
>
>
> On Wed, Jun 4, 2008 at 4:36 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
>
> > The stack trace says very clearly:
> > Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed
> > to authenticate. (or you have too old ssh2 installed, check with ssh2
> > -V)
> >
> > So, what does "ssh2 -V" say?
> >
> > Wayne
> >
> > On Wed, Jun 4, 2008 at 5:12 PM, Krishnamurthi, Venkat
> > <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > I'm trying to deploy a snapshot jar to a remote repository. I
> > > followed the instructions given here:
> > >
> > > http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-
> > > ssh-
> > > external.html
> > >
> > > However, when I execute mvn deploy, I get the following error:
> > >
> > > [INFO] [deploy:deploy]
> > > [INFO] Retrieving previous build number from scp_snapshot [WARNING]
> > > repository metadata for: 'snapshot demo:demo:1.0-SNAPSHOT'
> > > could not be retrieved from repository: scp_snapshot due to an
> error:
> > > Exit code: 78 - warning: Authentication failed.
> > > Disconnected (local); connection lost (Connection closed by remote
> > > host.).
> > > Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed
>
> > > to authenticate. (or you have too old ssh2 installed, check with
> > > ssh2 -V)
> > >
> > > [INFO] Repository 'scp_snapshot' will be blacklisted
> > > Uploading:
> > > scpexe://eqp2fcc:1080/scp_snapshot/demo/demo/1.0-SNAPSHOT/demo-1.0-S
> > > NAPS
> > > HOT.jar
> > > [INFO]
> > >
> > >
> > > [ERROR] BUILD ERROR
> > > [INFO]
> > >
> > > [INFO] Error deploying artifact: Error executing command for
> > > transfer
> > >
> > > Exit code 74 - warning: Authentication failed.
> > > Disconnected (local); connection lost (Connection closed by remote
> > > host.).
> > > Disconnect reason 10, exit code = 74
> > >
> > > My pom.xml has the following distributionManagement:
> > >
> > >
> > >
> > >
> > > false
> > > scp_snapshot
> > > SCP Snapshot Repository
> > > scpexe://eqp2fcc:1080/scp_snapshot
> > > default
> > >
> > >
> > >
> > > Also, I added the following to my settings.xml
> > >
> > >
> > >
> > > scp_snapshot
> > > my_username
> > > my_password
> > >
> > >
> > >
> > > Please help me resolve this issue.
> > >
> > >
> > > Thanks,
> > > Venkat
> > >
> > >
> > > - 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]
> >
> >
>
>
> --
> ---
> Thank You...
>
> Mick Knutson
> BASE Logic, inc.
>
> Website: http://baselogic.com
> Blog: http://baselogic.com/blog
> BLiNC Magazine: http://blincmagazine.com Linked IN:
> http://linkedin.com/in/mickknutson
> DJ Mick: http://djmick.com
> MySpace: http://myspace.com/mickknutson
> Tahoe: http://tahoe.baselogic.com
>
> -
RE: Error deploying to a remote respository using scm
Hi, I get the same error when I execute ssh2 -V on my windows XP machine: C:\ssh2 -V 'ssh2' is not recognized as an internal or external command, operable program or batch file. Please help me resolve this. Thanks, Venkat -Original Message- From: Mick Knutson [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 04, 2008 7:40 PM To: Maven Users List Subject: Re: Error deploying to a remote respository using scm on XP, I use that command adn get: *C:\opt\baselogic>ssh2 -V 'ssh2' is not recognized as an internal or external command, operable program or batch file. C:\opt\baselogic>ssh -V 'ssh' is not recognized as an internal or external command, operable program or batch file. C:\opt\baselogic> * Then when I try to deploy with scpexe it does the same thing. On Wed, Jun 4, 2008 at 4:36 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > The stack trace says very clearly: > Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed > to authenticate. (or you have too old ssh2 installed, check with ssh2 > -V) > > So, what does "ssh2 -V" say? > > Wayne > > On Wed, Jun 4, 2008 at 5:12 PM, Krishnamurthi, Venkat > <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I'm trying to deploy a snapshot jar to a remote repository. I > > followed the instructions given here: > > > > http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy- > > ssh- > > external.html > > > > However, when I execute mvn deploy, I get the following error: > > > > [INFO] [deploy:deploy] > > [INFO] Retrieving previous build number from scp_snapshot [WARNING] > > repository metadata for: 'snapshot demo:demo:1.0-SNAPSHOT' > > could not be retrieved from repository: scp_snapshot due to an error: > > Exit code: 78 - warning: Authentication failed. > > Disconnected (local); connection lost (Connection closed by remote > > host.). > > Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed > > to authenticate. (or you have too old ssh2 installed, check with > > ssh2 -V) > > > > [INFO] Repository 'scp_snapshot' will be blacklisted > > Uploading: > > scpexe://eqp2fcc:1080/scp_snapshot/demo/demo/1.0-SNAPSHOT/demo-1.0-S > > NAPS > > HOT.jar > > [INFO] > > > > > > [ERROR] BUILD ERROR > > [INFO] > > > > [INFO] Error deploying artifact: Error executing command for > > transfer > > > > Exit code 74 - warning: Authentication failed. > > Disconnected (local); connection lost (Connection closed by remote > > host.). > > Disconnect reason 10, exit code = 74 > > > > My pom.xml has the following distributionManagement: > > > > > > > > > > false > > scp_snapshot > > SCP Snapshot Repository > > scpexe://eqp2fcc:1080/scp_snapshot > > default > > > > > > > > Also, I added the following to my settings.xml > > > > > > > > scp_snapshot > > my_username > > my_password > > > > > > > > Please help me resolve this issue. > > > > > > Thanks, > > Venkat > > > > > > - 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] > > -- --- Thank You... Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: "temporary pom" for building project and dependencies?
David; Am Thu, 5 Jun 2008 09:01:38 +0200 schrieb David Delbecq <[EMAIL PROTECTED]>: > You can create a modules based pom that will build all your projects. > http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Aggregation Thanks a bunch, this indeed is quite what I was looking for, works like a charm. :) Now I only need to find a way to make my NetBeans automatically create such an "aggregated" pom (following Example 4) by sorting dependent modules in the right order. But that's another thing I guess. :) Thanks loads and best regards, Kristian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Need advice about adding native dependencies
Hi, for qt 4.4 one native jar is +/- 17MB ... I think you'd better ask the jambi mailing list as the possibility to create reduced native jar according to the application needs is jambi specific and not maven cheers, Etienne PS: I'll try to make splitted jars when my other todos are solved ;-) -Original Message- From: Haim Ashkenazi [mailto:[EMAIL PROTECTED] Sent: jeudi 5 juin 2008 14:57 To: Maven Users List Subject: Re: Need advice about adding native dependencies Hi On Thu, Jun 5, 2008 at 3:14 PM, Charlier, Etienne <[EMAIL PROTECTED]> wrote: > Hello, > > I'm busy right now trying to implement Option 3. based on jambi 4.4 > preview (they now distribute platform specific jars containing the > native code) > > - I wrote a shell script that > - downloads the jambi jar ( linux 32, linux 64, win 32 for now) > - unpack them > - deploy the java jar to my local nexus repository ( using fake groupid > ech.trolltech) > groupId = ech.trolltech > artifactId = qtjambi > version = 4.4.0_01 > - deploy the natives jar with > groupId = ech.trolltech > artifactId = qtjambi-native > classifier = linux32-gcc | linux64-gcc | win32-msvc2005 > version = 4.4.0_01 > - I also created a qtjambi-deps pom project having depedencies > - qt-jambi > - qt-jambi-natives > I used profiles activated using the stance to compute the > actual classifier based on the running platform... > > Now, creating a project depending on qt-jambi-deps should bring in the > correct native jar Actually you're not using option 3 :). You're importing all your native libraries into the project (which for linux32 is 37mb). Although I didn't try it yet, You should be able to import only some of them If you don't reference them in your code. I just don't want the size of the small utility I'm writing to be 40mb because of unneeded libraries. In option 3 I've meant to install each library on it's own as a libXXX.so file (which is probably impossible). Thanks for your answer anyway. I'll probably use your idea of a script to install a jar with all native libs locally and then hand-pick them in the packaging stage (option 4). Bye -- Haim - 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: Need advice about adding native dependencies
Hi On Thu, Jun 5, 2008 at 3:14 PM, Charlier, Etienne <[EMAIL PROTECTED]> wrote: > Hello, > > I'm busy right now trying to implement Option 3. based on jambi 4.4 > preview (they now distribute platform specific jars containing the > native code) > > - I wrote a shell script that > - downloads the jambi jar ( linux 32, linux 64, win 32 for now) > - unpack them > - deploy the java jar to my local nexus repository ( using fake groupid > ech.trolltech) > groupId = ech.trolltech > artifactId = qtjambi > version = 4.4.0_01 > - deploy the natives jar with > groupId = ech.trolltech > artifactId = qtjambi-native > classifier = linux32-gcc | linux64-gcc | win32-msvc2005 > version = 4.4.0_01 > - I also created a qtjambi-deps pom project having depedencies > - qt-jambi > - qt-jambi-natives > I used profiles activated using the stance to compute the > actual classifier based on the running platform... > > Now, creating a project depending on qt-jambi-deps should bring in the > correct native jar Actually you're not using option 3 :). You're importing all your native libraries into the project (which for linux32 is 37mb). Although I didn't try it yet, You should be able to import only some of them If you don't reference them in your code. I just don't want the size of the small utility I'm writing to be 40mb because of unneeded libraries. In option 3 I've meant to install each library on it's own as a libXXX.so file (which is probably impossible). Thanks for your answer anyway. I'll probably use your idea of a script to install a jar with all native libs locally and then hand-pick them in the packaging stage (option 4). Bye -- Haim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: modifying version number in POM
Hi Simon, Thanks a lot for that reply. Yes, I have a workflow in ANT (with CVS), which asks the user whether he wants a timestamp or a version build. With that as a mindset, I was looking on Maven. You have identified it right that Maven has its own stuff when it comes to versioning the builds. We are trying to migrate from ANT-CVS to Maven-SVN. :), and as far as possible, retain the workflow that's in place with ANT system, so that the people taking builds o maven, will feel at home ;). I think the release plugin already has everything for the versioning/tagging. Any comments? On 6/5/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I don't think this information is what Niranjan is really looking for. > > He appears to have some workflow that he is used to with some other > build tool, and is trying to use Maven to reproduce that same workflow. > But my guess is that it isn't a workflow that maven is designed to > implement, hence the confusion. > > Nirijan, why don't you try and describe what you are trying to do with > Maven then people can perhaps help you. > > For example, are you using this to do daily builds for the use of an > internal dev team, or are you releasing to customers? Are these > artefacts that you are trying to create just temporary or do they need > to be available a year from now? What version control system are you > using, and what changes do you want to happen in it when you do whatever > it is you are trying to do? > > Normally, for the purposes of internal development on a large project > you should set up a "snapshot" repository on some central computer. Then > periodically you deploy a snapshot to this repository. By default, two > copies are uploaded: one named "foo-SNAPSHOT.jar", and one named > "foo-SNAPSHOT-20080601100533.jar". Other people's poms can either add a > dependency on the "-SNAPSHOT" or "-SNAPSHOT-20080601100533" one. If they > use the first form, then as soon as someone publishes a new snapshot, > their computer will download it. That's good because they will pick up > bugfixes and see API changes. But it's bad because it might break their > build when they don't want to, so people who want some more stability > can depend on the dated version instead. > > Note that the pom tag does NOT need to get changed when > deploying a new snapshot to the snapshot repository. And so a new > version of pom.xml does not get checked in. > > But you should not release any code to customers that has a SNAPSHOT > dependency, because there is no way you can recreate that build. The > jarfile remains in the repo, but you can't be sure exactly what version > of the code it was built from. > > So before a real release, you update the pom to be a non-snapshot > version, check it in, tag it, build a jarfile and deploy it to a > non-snapshot repository, then update the pom again to have a -SNAPSHOT > version. > > If any of this is confusing, then please read the maven books that are > available on-line (see the maven website). > > Regards, > Simon > > Andreas Christoforides schrieb: > > Niranjan, > > > > The maven release plugin allows performing a dry run of the prepare goal > [1]. > > > > mvn release:prepare -DdryRun=true > > > > The dry run performs all the local file changes but without executing any > SCM > > operations (commits and tagging). > > > > To revert the file changes from the dry run you can also use the clean > goal: > > > > mvn release:clean > > > > Andreas > > > > [1] http://maven.apache.org/plugins/maven-release-plugin/usage.html > > > > On Wednesday 04 June 2008 11:49:34 pm Niranjan Deshpande wrote: > > > >> Hi Chris, > >> > >> So you meant to say that SNAPSHOT will be repaced by a timestamp at the > run > >> time? > >> also, can we avoid the chekin of the pom and tagging of the project that > >> happens after mvn release:prepare? i am rather experimenting on things > >> and dnt want to invite the wrath of other developers if ther repository > is > >> contaminated ;) > >> > >> On 6/5/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >> > >>> Mark Struberg <[EMAIL PROTECTED]> wrote on 04/06/2008 22:53:35: > >>> > Maybe i missed the point, or you did. > > The usual behaviour is to always have a SNAPSHOT version in your SCM > e.g. 1.4-SNAPSHOT > > If you make a build, you simply use the maven-release-plugin > > $>mvn release:prepare > this will > .) ask you the release-version which will default to 1.4 and the next- > version which defaults to 1.5-SNAPSHOT > .) does some usefull checks > .) checkin pom with the 1.4 into SCM and tag the project > .) set the next version in the pom to 1.5-SNAPSHOT or whatever you > provided in step 1 > > after this, do a > $>mvn release:perform > to build the project with the freshly tagged build version > > So there is usually no need to set versions in the pom manually. > > >>> So long as maven supports your scm...
RE: Need advice about adding native dependencies
Hello, I'm busy right now trying to implement Option 3. based on jambi 4.4 preview (they now distribute platform specific jars containing the native code) - I wrote a shell script that - downloads the jambi jar ( linux 32, linux 64, win 32 for now) - unpack them - deploy the java jar to my local nexus repository ( using fake groupid ech.trolltech) groupId = ech.trolltech artifactId = qtjambi version = 4.4.0_01 - deploy the natives jar with groupId = ech.trolltech artifactId = qtjambi-native classifier = linux32-gcc | linux64-gcc | win32-msvc2005 version = 4.4.0_01 - I also created a qtjambi-deps pom project having depedencies - qt-jambi - qt-jambi-natives I used profiles activated using the stance to compute the actual classifier based on the running platform... Now, creating a project depending on qt-jambi-deps should bring in the correct native jar TODO: - check all this by creating a small hello world program with qt-jambi - use the assembly plugin to create platform specifics jar-with-dependencies for deployement on user's computers BTW, I already touched that topic on the jambi mailing list asking for a maven repository managed by trolltech hosting those artifacts... without much success ( licensing issues ...) Cheers Etienne -Original Message- From: Haim Ashkenazi [mailto:[EMAIL PROTECTED] Sent: jeudi 5 juin 2008 12:57 To: Maven Users List Subject: Need advice about adding native dependencies Hi I'm creating a project that uses qtjambi (QT's java binding - http://trolltech.com/products/qt/features/language-support/java). It has both jar files and native libraries (statically compiled - seems to be working fine at least on a few linuxes I've tried). In their deployment documentation they recommend adding the native libraries to the jar (top level) plus a descriptor file. Also you may not need all the native libraries in your application (total of 37MB for linux32). you may only need a few of them. I have a few options here and I need you advice: Option 1: Create an ANT script that downloads the binary zip/tar.gz file, creates a customized jar (optimized for my project) and deploys it to my local repository. Since this is a customize jar I need to give it a unique groupId (i.e. not "com.trolltech.qtjambi") because otherwise if I'll have another project that used qtjambi with different settings it'll overwrite it. Option 2: Create a custom jar like above but put it somewhere in the system and use a "system" dependency. Option 3: (I'm not sure if it's even technically possible) deploy the original qtjambi.jar (without native libraries) to my archiva server and also deploy the native libs as files into the server and somehow declare each native library as a dependency . If it's possible, I guess this would be my favorite option. Option 4: Create a full jar with the native libs inside or in a separate jar, deploy it (either on a server, or locally by script) and hand-pick the parts I need manually in the packaging stage. Is there a "correct" way to do it? thanx -- Haim - 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]
Need advice about adding native dependencies
Hi I'm creating a project that uses qtjambi (QT's java binding - http://trolltech.com/products/qt/features/language-support/java). It has both jar files and native libraries (statically compiled - seems to be working fine at least on a few linuxes I've tried). In their deployment documentation they recommend adding the native libraries to the jar (top level) plus a descriptor file. Also you may not need all the native libraries in your application (total of 37MB for linux32). you may only need a few of them. I have a few options here and I need you advice: Option 1: Create an ANT script that downloads the binary zip/tar.gz file, creates a customized jar (optimized for my project) and deploys it to my local repository. Since this is a customize jar I need to give it a unique groupId (i.e. not "com.trolltech.qtjambi") because otherwise if I'll have another project that used qtjambi with different settings it'll overwrite it. Option 2: Create a custom jar like above but put it somewhere in the system and use a "system" dependency. Option 3: (I'm not sure if it's even technically possible) deploy the original qtjambi.jar (without native libraries) to my archiva server and also deploy the native libs as files into the server and somehow declare each native library as a dependency . If it's possible, I guess this would be my favorite option. Option 4: Create a full jar with the native libs inside or in a separate jar, deploy it (either on a server, or locally by script) and hand-pick the parts I need manually in the packaging stage. Is there a "correct" way to do it? thanx -- Haim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: modifying version number in POM
I don't think this information is what Niranjan is really looking for. He appears to have some workflow that he is used to with some other build tool, and is trying to use Maven to reproduce that same workflow. But my guess is that it isn't a workflow that maven is designed to implement, hence the confusion. Nirijan, why don't you try and describe what you are trying to do with Maven then people can perhaps help you. For example, are you using this to do daily builds for the use of an internal dev team, or are you releasing to customers? Are these artefacts that you are trying to create just temporary or do they need to be available a year from now? What version control system are you using, and what changes do you want to happen in it when you do whatever it is you are trying to do? Normally, for the purposes of internal development on a large project you should set up a "snapshot" repository on some central computer. Then periodically you deploy a snapshot to this repository. By default, two copies are uploaded: one named "foo-SNAPSHOT.jar", and one named "foo-SNAPSHOT-20080601100533.jar". Other people's poms can either add a dependency on the "-SNAPSHOT" or "-SNAPSHOT-20080601100533" one. If they use the first form, then as soon as someone publishes a new snapshot, their computer will download it. That's good because they will pick up bugfixes and see API changes. But it's bad because it might break their build when they don't want to, so people who want some more stability can depend on the dated version instead. Note that the pom tag does NOT need to get changed when deploying a new snapshot to the snapshot repository. And so a new version of pom.xml does not get checked in. But you should not release any code to customers that has a SNAPSHOT dependency, because there is no way you can recreate that build. The jarfile remains in the repo, but you can't be sure exactly what version of the code it was built from. So before a real release, you update the pom to be a non-snapshot version, check it in, tag it, build a jarfile and deploy it to a non-snapshot repository, then update the pom again to have a -SNAPSHOT version. If any of this is confusing, then please read the maven books that are available on-line (see the maven website). Regards, Simon Andreas Christoforides schrieb: > Niranjan, > > The maven release plugin allows performing a dry run of the prepare goal [1]. > > mvn release:prepare -DdryRun=true > > The dry run performs all the local file changes but without executing any SCM > operations (commits and tagging). > > To revert the file changes from the dry run you can also use the clean goal: > > mvn release:clean > > Andreas > > [1] http://maven.apache.org/plugins/maven-release-plugin/usage.html > > On Wednesday 04 June 2008 11:49:34 pm Niranjan Deshpande wrote: > >> Hi Chris, >> >> So you meant to say that SNAPSHOT will be repaced by a timestamp at the run >> time? >> also, can we avoid the chekin of the pom and tagging of the project that >> happens after mvn release:prepare? i am rather experimenting on things >> and dnt want to invite the wrath of other developers if ther repository is >> contaminated ;) >> >> On 6/5/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> >>> Mark Struberg <[EMAIL PROTECTED]> wrote on 04/06/2008 22:53:35: >>> Maybe i missed the point, or you did. The usual behaviour is to always have a SNAPSHOT version in your SCM e.g. 1.4-SNAPSHOT If you make a build, you simply use the maven-release-plugin $>mvn release:prepare this will .) ask you the release-version which will default to 1.4 and the next- version which defaults to 1.5-SNAPSHOT .) does some usefull checks .) checkin pom with the 1.4 into SCM and tag the project .) set the next version in the pom to 1.5-SNAPSHOT or whatever you provided in step 1 after this, do a $>mvn release:perform to build the project with the freshly tagged build version So there is usually no need to set versions in the pom manually. >>> So long as maven supports your scm... >>> >>> -Chris >>> >>> >>> ** >>> CAUTION - This message is intended for the addressee named above. It may >>> contain privileged or confidential information. >>> >>> If you are not the intended recipient of this message you must: >>> - Not use, copy, distribute or disclose it to anyone other than the >>> addressee; >>> - Notify the sender via return email; and >>> - Delete the message (and any related attachments) from your computer >>> immediately. >>> >>> Internet emails are not necessarily secure. Australian Associated Motors >>> Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do >>> not accept responsibility for changes made to this message after it was >>> sent. >>> >>> Unless otherwise stated, views expressed within this em
Re: Profiles and Resources (wsdl)
The solution is to specify resources in maven-war-plugin http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html Kinski wrote: > > Hi, > > I am re-factoring a legacy web services app as a Maven project which is > now complete apart from one obstacle. I am using placeholders for any > variations relating to local, live and dev use. These are defined as > within each relevant in the pom.xml. > > All are resolving fine, bar one (the wsdl file) because it is required in > the webapp home (i.e. http://localhost:8080/appname/definitions/file.wsdl) > rather than within WEB-INF/classes (which is the default location for > ) > > Currently the file is stored in src/main/webapps/definitions > > To be clear, it resolves fine if I place the definitions folder in > src/main/resources but then it's destination in the war is > WEB-INF/classes/definitions/file.wsdl > (which is to be avoided if possible as the url is preferred not to change > as the app is already in live use) > > I have experimented with the alternative solution of using an additional > resource directory... > > > src/main/webapps > true > > > using for example ../tester > > But this actually creates the destination outside the war file. > > So my question is how can I get Maven to recognise my wsdl file as a > resource which needs its placholder resolved AND keep its destination > outside WEB-INF/classes in the root of the webapp? > > As I am new to web services, I am also curious if there are any best > practices relating to where a wsdl file should be stored within a webapp. > > Many Thanks, > > Matthew > - Regards, Matthew -- View this message in context: http://www.nabble.com/Profiles-and-Resources-%28wsdl%29-tp17649887p17665516.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: modifying version number in POM
> So long as maven supports your scm... But then it is still much better to get this SCM supported then having hundred of developers tweaking around manually. Which SCM you need isn't supported yet? Since I already wrote the maven-scm-providers-git, I maybe can help you in writing another one. LieGrü, strub --- [EMAIL PROTECTED] <[EMAIL PROTECTED]> schrieb am Do, 5.6.2008: > Mark Struberg <[EMAIL PROTECTED]> wrote on 04/06/2008 > 22:53:35: > > > Maybe i missed the point, or you did. > > > > The usual behaviour is to always have a SNAPSHOT > version in your SCM > > e.g. 1.4-SNAPSHOT > > > > If you make a build, you simply use the > maven-release-plugin > > > > $>mvn release:prepare > > this will > > .) ask you the release-version which will default to > 1.4 and the next- > > version which defaults to 1.5-SNAPSHOT > > .) does some usefull checks > > .) checkin pom with the 1.4 into SCM and tag the > project > > .) set the next version in the pom to 1.5-SNAPSHOT or > whatever you > > provided in step 1 > > > > after this, do a > > $>mvn release:perform > > to build the project with the freshly tagged build > version > > > > So there is usually no need to set versions in the pom > manually. > > So long as maven supports your scm... > __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: modifying version number in POM
The release-plugin will replace a version n-SNAPSHOT with n, then tag this version n and replace it again with (n+1)-SNAPSHOT All those versions will be prompted, but prefilled as default. so if you have a myproject-2.17-SNAPSHOT mvn release:prepare will create and tag a myproject-2.17 in the SCM. Essentially this turns your snapshot build into a full build! Afterwards, the version number will be increased to myproject-2.18-SNAPSHOT in the SCM automatically mvn release:perform will then deploy your tagged myproject-2.17 Btw, a SNAPSHOT version should almost never get to a non-private repo! LieGrü, strub --- Niranjan Deshpande <[EMAIL PROTECTED]> schrieb am Do, 5.6.2008: > Von: Niranjan Deshpande <[EMAIL PROTECTED]> > Betreff: Re: AW: modifying version number in POM > An: "Maven Users List" > Datum: Donnerstag, 5. Juni 2008, 8:49 > Hi Chris, > > So you meant to say that SNAPSHOT will be repaced by a > timestamp at the run > time? > also, can we avoid the chekin of the pom and tagging of the > project that > happens after mvn release:prepare? i am rather > experimenting on things > and dnt want to invite the wrath of other developers if > ther repository is > contaminated ;) > > > On 6/5/08, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > > > Mark Struberg <[EMAIL PROTECTED]> wrote on > 04/06/2008 22:53:35: > > > > > Maybe i missed the point, or you did. > > > > > > The usual behaviour is to always have a SNAPSHOT > version in your SCM > > > e.g. 1.4-SNAPSHOT > > > > > > If you make a build, you simply use the > maven-release-plugin > > > > > > $>mvn release:prepare > > > this will > > > .) ask you the release-version which will default > to 1.4 and the next- > > > version which defaults to 1.5-SNAPSHOT > > > .) does some usefull checks > > > .) checkin pom with the 1.4 into SCM and tag the > project > > > .) set the next version in the pom to > 1.5-SNAPSHOT or whatever you > > > provided in step 1 > > > > > > after this, do a > > > $>mvn release:perform > > > to build the project with the freshly tagged > build version > > > > > > So there is usually no need to set versions in > the pom manually. > > > > So long as maven supports your scm... > > > > -Chris > > > > > > > ** > > CAUTION - This message is intended for the addressee > named above. It may > > contain privileged or confidential information. > > > > If you are not the intended recipient of this message > you must: > > - Not use, copy, distribute or disclose it to anyone > other than the > > addressee; > > - Notify the sender via return email; and > > - Delete the message (and any related attachments) > from your computer > > immediately. > > > > Internet emails are not necessarily secure. Australian > Associated Motors > > Insurers Limited ABN 92 004 791 744 (AAMI), and its > related entities, do not > > accept responsibility for changes made to this message > after it was sent. > > > > Unless otherwise stated, views expressed within this > email are the author's > > own and do not represent those of AAMI. > > > ** > > > > > - > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > -- > Regards, > Niranjan Deshpande > > "Shut yourself from the world and create the reality > you want" __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: java.net.SocketException - need help in getting started
Thank you! that was the problem, all working now. -Gianni On 05/giu/08, at 07:29, Tim Kettler wrote: Hi, googling hints that it's a bug in the java sdk on freebsd. There is a similar bug report like yours for freebsd 6 posted for IDEA [1] which says that IPv6 support in the jdk is the problem. This [2] is another bug report of the same problem with the solution to set the JAVAVM_OPTS like this: export JAVAVM_OPTS_java=-Djava.net.preferIPv4Stack=true" And finally this bug was reported [3] on the freebsd-java list some time ago. Hope this helps -Tim [1] http://www.jetbrains.net/jira/browse/IDEA-15976 [2] http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2007-11/msg00220.html [3] http://lists.freebsd.org/pipermail/freebsd-java/2007-August/006544.html Gianni Doe schrieb: Hi, I'm completely new to maven and just trying out the "Maven in 5 Minutes" but not getting very far. When I try to create a new project I get the exception below; my machine has unimpeded access to the internet so the issue is not firewall related. I'd appreciate some suggestions. [EMAIL PROTECTED]:/data/Projects$ mvn -X archetype:create - DgroupId=com.test -DartifactId=testapp + Error stacktraces are turned on. Maven version: 2.0.9 Java version: 1.6.0_03-p4 OS name: "freebsd" version: "7.0-stable" arch: "amd64" Family: "unix" [DEBUG] Building Maven user-level plugin registry from: '/home/ shares/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/usr/ local/apache-maven/conf/plugin-registry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file [DEBUG] Exception org.apache.maven.wagon.TransferFailedException: Error transferring file at org .apache .maven .wagon .providers .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java: 104) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java: 68) at org .apache .maven .artifact .manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java: 470) at org .apache .maven .artifact .manager .DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java: 370) at org .apache .maven .artifact .repository .metadata .DefaultRepositoryMetadataManager .resolve(DefaultRepositoryMetadataManager.java:97) at org .apache .maven .plugin .DefaultPluginMappingManager .loadPluginMappings(DefaultPluginMappingManager.java:103) at org .apache .maven .plugin .DefaultPluginMappingManager .loadPluginMappings(DefaultPluginMappingManager.java:87) at org .apache .maven .plugin .DefaultPluginMappingManager .getByPrefix(DefaultPluginMappingManager.java:61) at org .apache .maven .plugin .DefaultPluginManager .getPluginDefinitionForPrefix(DefaultPluginManager.java:154) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .getMojoDescriptor(DefaultLifecycleExecutor.java:1468) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java: 405) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java: 137) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) 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:597) 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) Caused by: java.net.SocketException: Invalid argument at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java: 195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at sun.net.NetworkClient.doConnect(NetworkClient.java:157) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpCli
maven multiproject
Hi,Does the multiproject site works with maven 2.0.9,is there a separate plugin for it?It used to create separate sites for every subproject before,does it still do that.Kindly let me know. Thanks, Kalyana krishnan
How best to determine snapshot dependencies programmatically in a multi-module project
I am looking for a little help with the Maven API. If I have the file path to a pom.xml file that is the top level pom in a multi-module project, how do I (using the Maven API) load that top level pom and also recurse down to the sub-module poms and come up with a list of all of the SNAPSHOT dependencies - preferably I would like to get both regular dependencies and also plugin dependencies. Looking at the API, I think I can use the MavenEmbedder object to do a lot of this, but I can't quite get all the pieces together - particular how to discover if a pom has sub-modules and how to navigate to them. Any help is greatly appreciated. Cheers -- Craig Dickson Software Engineering Manager Behr Process Corporation Santa Ana, California
Re: AW: modifying version number in POM
Niranjan, The maven release plugin allows performing a dry run of the prepare goal [1]. mvn release:prepare -DdryRun=true The dry run performs all the local file changes but without executing any SCM operations (commits and tagging). To revert the file changes from the dry run you can also use the clean goal: mvn release:clean Andreas [1] http://maven.apache.org/plugins/maven-release-plugin/usage.html On Wednesday 04 June 2008 11:49:34 pm Niranjan Deshpande wrote: > Hi Chris, > > So you meant to say that SNAPSHOT will be repaced by a timestamp at the run > time? > also, can we avoid the chekin of the pom and tagging of the project that > happens after mvn release:prepare? i am rather experimenting on things > and dnt want to invite the wrath of other developers if ther repository is > contaminated ;) > > On 6/5/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Mark Struberg <[EMAIL PROTECTED]> wrote on 04/06/2008 22:53:35: > > > Maybe i missed the point, or you did. > > > > > > The usual behaviour is to always have a SNAPSHOT version in your SCM > > > e.g. 1.4-SNAPSHOT > > > > > > If you make a build, you simply use the maven-release-plugin > > > > > > $>mvn release:prepare > > > this will > > > .) ask you the release-version which will default to 1.4 and the next- > > > version which defaults to 1.5-SNAPSHOT > > > .) does some usefull checks > > > .) checkin pom with the 1.4 into SCM and tag the project > > > .) set the next version in the pom to 1.5-SNAPSHOT or whatever you > > > provided in step 1 > > > > > > after this, do a > > > $>mvn release:perform > > > to build the project with the freshly tagged build version > > > > > > So there is usually no need to set versions in the pom manually. > > > > So long as maven supports your scm... > > > > -Chris > > > > > > ** > > CAUTION - This message is intended for the addressee named above. It may > > contain privileged or confidential information. > > > > If you are not the intended recipient of this message you must: > > - Not use, copy, distribute or disclose it to anyone other than the > > addressee; > > - Notify the sender via return email; and > > - Delete the message (and any related attachments) from your computer > > immediately. > > > > Internet emails are not necessarily secure. Australian Associated Motors > > Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do > > not accept responsibility for changes made to this message after it was > > sent. > > > > Unless otherwise stated, views expressed within this email are the > > author's own and do not represent those of AAMI. > > ** > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > -- > Regards, > Niranjan Deshpande > > "Shut yourself from the world and create the reality you want" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: checkstyle problem with maven : Unable to instantiate TreeWalker
Thanks for the answer. So, I tried maven-checkstyle-plugin 2.2 and it didn't work either, but that's a good beginning to have the correct plugin version... In the xml checkstyle configuration file where modules are defined, i tried to change by and it now works. I don't really understand why we have to specify the fully qualified name of this class, because it works fine when not using maven. On Wed, Jun 4, 2008 at 11:47 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > The Checkstyle plugin version 2.1 uses Checkstyle 4.1. So you can't use > stuff from Checkstyle 4.3 in your Checkstyle configuration. > > Version 2.2 of the plugin, which is being released as we speak, uses > Checkstyle 4.4. Start by giving that version a try. > > > Julien Simon wrote: > >> Hi, >> I'm trying to integrate a checkstyle report in a maven project, but I'm >> facing a problem. The checkstyle report is based on a custom checkstyle >> check module I developed. >> I'm using maven 2.0.9, maven-checkstyle-plugin 2.1, and checkstyle 4.3 >> >> When I execute mvn checkstyle:checkstyle or mvn site, I get the following >> exception. I don't really understand why the TreeWalker can't be >> instantiated. >> >> Any help would be great! >> >> >> >> >> [ERROR] BUILD ERROR >> [INFO] >> >> [INFO] An error has occurred in Checkstyle report generation. >> >> Embedded error: Failed during checkstyle configuration >> Unable to instantiate TreeWalkerCheck >> [INFO] >> >> [DEBUG] Trace >> org.apache.maven.lifecycle.LifecycleExecutionException: An error has >> occurred in Checkstyle report generation. >>at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) >>at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) >>at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) >>at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) >>at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) >>at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) >>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) >>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) >>at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) >>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>at >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) >>at >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>at java.lang.reflect.Method.invoke(Method.java:615) >>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) >> Caused by: org.apache.maven.plugin.MojoExecutionException: An error has >> occurred in Checkstyle report generation. >>at >> >> org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:79) >>at >> >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) >>at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) >>... 16 more >> Caused by: org.apache.maven.reporting.MavenReportException: Failed during >> checkstyle configuration >>at >> >> org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:488) >>at >> >> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98) >>at >> >> org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:73) >>... 18 more >> Caused by: com.puppycrawl.tools.checkstyle.api.CheckstyleException: cannot >> initialize module TreeWalker - Unable to instantiate TreeWalker >>at com.puppycrawl.tools.checkstyle.Checker.setupChild(Checker.java:165) >>at >> >> com.puppycrawl.tools.checkstyle.api.AutomaticBean.configure(AutomaticBean.java:209) >>at >> >> org.apache.maven.plugin.checkstyle.CheckstyleReport.executeCheckstyle(CheckstyleReport.java:723) >>at >> >> org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:484) >>... 20 more >> Caused by: com.puppycrawl.tools.checkstyle.api.CheckstyleException: Unable >> to instantiate TreeWalker >>at >> >> com.puppycrawl.tools.checkstyle.PackageObjectFactory.createModule(PackageObjectFactory.java:152) >>at com.puppycrawl.tools.checkstyle.Checker.setupChild(Chec
Re: "temporary pom" for building project and dependencies?
You can create a modules based pom that will build all your projects. http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Aggregation Le Thursday 05 June 2008 08:15:22 Kristian Rink, vous avez écrit : > Folks; > > not sure whether this is a "common" use case, I wonder what's a good > way to have the following scenario done. We handle our projects using > maven2, and we are used to have things split up: > > - There's a "core" project (jar) of the application which includes > commonly used classes and interfaces needed in all other applications. > > - There are some "components" projects (jars, as well), depending upon > "core", used in some of the business applications. > > - There are a bunch of, say, war artifacts offering exposing web > interfaces or web services, depending upon various "components". > > My problem, by now, is that, in case of some change tthat cross these > module boundaries, I have to rebuild altogether "core", a few > "components" packages and the war artifact relying upon them. My > question is whether there is some way to, in case these projects are > independent, "abuse" maven to have, say, "core" and a set of > "components" automatically built and installed along with (and > possibly before) building the war artifact depending upon them? Is > there a common way of doing so, or should I reconsider my project > structure? > > TIA and best regards, > Kristian > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- David Delbecq Institut Royal Météorologique Ext 557 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
