'Enter' Breakline not taken in account
Hi,
When I execute this program without Maven :
publicclass Main {publicstaticvoid main(String[] args)throws IOException {
BufferedReader br = new BufferedReader(new InputStreamReader(System.in));
String chaine = br.readLine(); System.out.println(la chaine : + chaine);}}
Everything is ok : what I write on the keyboard is correctly printed on screen.
But if I execute the same program on a Maven project, it can't detect my
breakline when I press Enter, and the program ever waits the string end and
then it doesn't print what I've written on the screen.
How can I solve this problem ?
Thanks in advance.
Re: Selective repo purge after clean install
Thank you for the reply Wayne! I will try modifying the plugin for my use. I just wanted to ensure I wasn't re-inventing the wheel. Thanks, Zeba -- View this message in context: http://maven.40175.n5.nabble.com/Selective-repo-purge-after-clean-install-tp5603961p5606133.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how to custom decrypt settings.xml passwords
hi all there is however something that bothers me: I wrote a plugin that access the Settings object. That object is instantiated by maven, and contains the merge of all settings available (M2_HOME/conf/settings.xml, ~/.m2/settings.xml and -s settings.xml). with my plugin, I look after my corporate encoded passwords, decode them, and update the Settings object with the decoded value. I linked my plugin with initialize, generate-resources and process-resources phases. My debug shows me that at the very first phase (initialize), the Settings object is well updated (password decrypted using our corporate tool), and the two next phases show the correctly updated Settings object - having the passwords decrypted. However, when maven goes for downloading dependencies, it fails because maven takes the encrypted version of the password. IMHO, I think that maven reads again the settings.xml file, whether it should use the Settings object. Has someone some feedback for that? thanks for your reading On 13 March 2012 14:59, Lyons, Roy roy.ly...@cmegroup.com wrote: To address the issue of weak encryption of passwords, CME Group has contracted with Sonatype to create a custom build of Nexus that uses ssh keys and PKI for authentication. We are expecting to receive a delivery early to mid April on the ssh based approach. The PKI approach will require some customization on the maven client end, to allow for certificate based authentication. You may want to contact Sonatype to address your issues, they will have a solution. Thanks, Roy -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Tuesday, March 13, 2012 4:41 AM To: Maven Users List Subject: Re: how to custom decrypt settings.xml passwords I don't think this is possible to do through a Maven plugin. It has to be part of Maven core. Unfortunately, Maven Core currently does not (that I've found) provide with a hook or extension to switch the encryption mechanism. Until that is implemented, I believe you need to create your own extended Maven installation with support for this. I'm in a similar situation. For a corporate environment with fairly high security concerns, the current solution with passwords in settings.xml is a problem in general. Also, it causes problems on CI as the credentials are quite easy to get hold of (a simple Maven build will reveal it). So, currently, we've not allowed CI to deploy artifacts to the repo. So, from my perspective there are different things to solve (in my case at least): * A simpler/better solution to handle the users' credentials. This could be integration with smart cards, Windows SSO (kerberos?), etc. The user shouldn't have to update the settings.xml. * A good/secure integration between CI and the repo. Ultimately I'd like the end user's credentails to be used (not a generic CI account as I want to know exactly who pressed the build button). If a generic CI account is used, it has to be kept outside of the Maven Core loop so that it can't be snooped. /Anders On Tue, Mar 13, 2012 at 10:07, Lannoye Xavier lannoye.xav...@gmail.com wrote: Hi I'm working in a corporate environment, with maven builds processed on atlassian bamboo servers. I've been asked to investigate a solution to encrypt passwords present in the custom settings.xml file against our corporate encryption software. I've started with the maven's master-password procedure, but with this procedure, we faced the distributed bamboo's remote agents issue. passwords must be encrypted using the master password of the server it is going to be decrypted later on, and with bamboo agents, you cannot guarantee on which server the build will be executed. Then I read about ssh encrypted passwords, but this requires ssh login for each of our customers on our servers, which they don't have. We have to many users to create unix accounts for each of them, and furthermore, we don't want them to access our servers by other meanings than the bamboo interface. Not mentioning they should have access to every remote agent. so this is why we finally get to the point we need to force our bamboo users to include in their project their own settings.xml file, which they call in their build with the -s parameter. in settings.xml however, the passwords are plain text, and so are readable by anyone. I was thinking about writing a maven plugin which could use our corporate encryption software to decrypt passwords. But I cannot figure out how to hook this inside maven. I already wrote a plugin that reads the settings.xml file, but how to push the decrypted password inside the maven build process? I'd need something as a hook but cannot find any. Thanks for everyone for taking the time to read this (quite) long message. - To unsubscribe,
Re: 'Enter' Breakline not taken in account
But if I execute the same program on a Maven project, it can't detect my breakline when I press Enter, and the program ever waits the string end and then it doesn't print what I've written on the screen. What exact command line are you using to execute the same program on a Maven project? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Avoiding duplicate POM code: profiles, inheritance, properties
Hello all, I'm currently working in several projects using maven 3, and I need some help defining a new POM hierarchy to avoid POM code duplication. My projects are composed of multiple bundles (it's OSGi based). Each project has its own deployment and source repositories and defines a different set of bundles, but all bundles in all projects are sharing common basic configurations. Note: I don't use the word project in the meaning of maven project (that is, a project is a bunch of bundles, each bundle being a single maven project). For now, each project is totally independent and has its own POM hierarchy: The deployment POM : top most POM, contains project specific properties (deployment repository, scm, developers...). The common POM : next one in the hierarchy tree, contains common features (dependencies, plugin configurations...). The type POMs : the third hierarchy level has several POMs, each one with features for a specific bundle type (web bundle, persistence bundle...). The common POM and some of the type POMs have different profiles corresponding to different build targets (onboard, offboard...). This way, each bundle defines its type by inheriting from the right parent, and building for a given target is done through profile activation on the command-line (ex. mvn install -P onboard). It is working, but, bundle types being the same for all projects, parent POMs are almost identical. I just copy the POM hierarchy into each new project, changing only the properties of the deployment POM. The build infrastructure and deployment process being still a work in progress, the POMs are changing quite often and the maintenance of all those duplicated configs is becoming really annoying. So here am I, looking for answers. What I would like to do is package all technical stuff (dependencies, plugin configurations) in global POM(s) being shared by all projects, and leave management properties (the deployment POM) inside each project. What I tried: The current approach forbid this because the deployment POM is at the top of the hierarchy. Because there is multiple leaf POMs (the type POMs), putting deployment at the bottom would need multiple project specific POMs, each one inheriting from a type POM. Some kind of proxy POMs adding properties along the way. But then deployment information would be duplicated. Not good enough. Unless there is a way to put those information in a property file, and use it in all those proxys. But I don't know how to do that. I also tried to group all type POMs into one single POM with profiles. One profile by type, activated by a marker file in the inheriting bundle (didn't find any other way to activate a parent profile from a child artifact). But then the target specific behavior is not working anymore, because profile activations are ORed together, so I cannot create a profile running only for the persistence type AND the onboard target. So this is not working either. Now, I start wondering if I'm not asking maven more than it can manage. Not the first time I struggle with its poor inheritance capabilities and the lack of an include feature (heard about mixins, but seems it won't be there before a long time). Thanks in advance to all people who will reach the end of this really long post (if any). Regards, Thomas GILLET - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Avoiding duplicate POM code: profiles, inheritance, properties
I read it to the end but I am not sure that I got it all. One suggestion that we found helpful is to start to look at some of the maven projects as utilities that are really no different from a developers point of view than utilities that we use from Apache or Springframework or others. They get their own lifecycle and live in our Nexus where all projects can use them as dependencies. I am not sure why you have more than one deployment repo since you should be able to separate things out by their GAV and possibly classifiers. Like you, each of our applications has a parent pom maven project and a bunch of maven projects that create - jars that are dependencies for other projects - jars that are executables - wars that are webapps. These are all held in the single repo since they all have unique GAVs. There is no reason why each project could not have its own repo. I can only think of internal security or secrecy as generating this requirement. I am not sure that I have advanced your cause in any way except perhaps in the area of separating applications from utilities. Perhaps others who use OSGI might be able to advance the conversation a bit more. Ron On 30/03/2012 9:36 AM, Gillet Thomas (2) wrote: Hello all, I'm currently working in several projects using maven 3, and I need some help defining a new POM hierarchy to avoid POM code duplication. My projects are composed of multiple bundles (it's OSGi based). Each project has its own deployment and source repositories and defines a different set of bundles, but all bundles in all projects are sharing common basic configurations. Note: I don't use the word project in the meaning of maven project (that is, a project is a bunch of bundles, each bundle being a single maven project). For now, each project is totally independent and has its own POM hierarchy: The deployment POM : top most POM, contains project specific properties (deployment repository, scm, developers...). The common POM : next one in the hierarchy tree, contains common features (dependencies, plugin configurations...). The type POMs : the third hierarchy level has several POMs, each one with features for a specific bundle type (web bundle, persistence bundle...). The common POM and some of the type POMs have different profiles corresponding to different build targets (onboard, offboard...). This way, each bundle defines its type by inheriting from the right parent, and building for a given target is done through profile activation on the command-line (ex. mvn install -P onboard). It is working, but, bundle types being the same for all projects, parent POMs are almost identical. I just copy the POM hierarchy into each new project, changing only the properties of the deployment POM. The build infrastructure and deployment process being still a work in progress, the POMs are changing quite often and the maintenance of all those duplicated configs is becoming really annoying. So here am I, looking for answers. What I would like to do is package all technical stuff (dependencies, plugin configurations) in global POM(s) being shared by all projects, and leave management properties (the deployment POM) inside each project. What I tried: The current approach forbid this because the deployment POM is at the top of the hierarchy. Because there is multiple leaf POMs (the type POMs), putting deployment at the bottom would need multiple project specific POMs, each one inheriting from a type POM. Some kind of proxy POMs adding properties along the way. But then deployment information would be duplicated. Not good enough. Unless there is a way to put those information in a property file, and use it in all those proxys. But I don't know how to do that. I also tried to group all type POMs into one single POM with profiles. One profile by type, activated by a marker file in the inheriting bundle (didn't find any other way to activate a parent profile from a child artifact). But then the target specific behavior is not working anymore, because profile activations are ORed together, so I cannot create a profile running only for the persistence type AND the onboard target. So this is not working either. Now, I start wondering if I'm not asking maven more than it can manage. Not the first time I struggle with its poor inheritance capabilities and the lack of an include feature (heard about mixins, but seems it won't be there before a long time). Thanks in advance to all people who will reach the end of this really long post (if any). Regards, Thomas GILLET - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 -
RE: Avoiding duplicate POM code: profiles, inheritance, properties
Hello Ron, I'm not sure I understand what you meant... My problem is all about the POMs, that is, how can I share pieces of configuration (i.e pieces of POM file) between bundles, the main problems being that I have not a single inheritance chain (because of project specific deployment properties and target specific configuration). The real artifacts (the ones with actual code in it, that is, the bundles) are not really part of the problem. So I fail to see the link with the utilities... Unless maybe you were implying that a POM can use another POM the same way a bundle can use a library (which would indeed be the solution to all my problems), but I don't know how to do that. The fact that we have multiple repositories is just a convenience. We split up our Artifactory into several sub-repositories so we can manage permissions of each developer differently for each repo (that is, for each project). We would have been using one big repo if it had helped, but still remains the per-project SVN repos which we want to keep like that. So using the release plugin for example would still require at least this property to be specific to each project. That is maybe a lot of wondering just for one property (well, one for now, but who knows). Still, I really hate duplicate stuff. Read my post again, and that's indeed not so clear what I am speaking about. I should rewrite the question. Anyway, thanks for your answer. Thomas GILLET - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Different behavior when building a project as a module or stand-alone
Hello, When trying to set up an assembly for a project, I ran into a problem I can't seem to find an explanation for. My project has a basic multi-module structure, like this : The thing is, I get two different results for executing /mvn clean package/, whether I run it from /project-core/ or from /project/. *From project-core* *From project* And indeed, the .jar is empty (safe a couple of metadata files), which cause the build to fail on /project-web/, which depends on /project-core/ The main oddities I have set up for the build are : 1) maven-dependency-plugin:purge-local-repository, executed at /prepare-package/ for /project-core/ only 2) maven-assembly-plugin:single, executed at /package/ for the web and batch projects, but the global build fails before they even kick in ;) I did not configure the /maven-jar-plugin/, so this is what I have in the effective pom : I'm using Maven 3.0.3, and a 1.6.0_24 JDK if it makes any difference. Sorry if this problem is common knowledge, I just didn't know what to search for in the mailing list ! Thank you ! Philippe -- View this message in context: http://maven.40175.n5.nabble.com/Different-behavior-when-building-a-project-as-a-module-or-stand-alone-tp5607081p5607081.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Avoiding duplicate POM code: profiles, inheritance, properties
My problem is all about the POMs, that is, how can I share pieces of configuration (i.e pieces of POM file) between bundles, the main problems being that I have not a single inheritance chain (because of project specific deployment properties and target specific configuration). I'm not sure that I understand your problem very well either. I can offer up a few bits that may be helpful. 1. Inheritance does not necessarily follow aggregation. As an example: Project A with modules SubAA, SubAB, SubAC + Project SubAA [parent is A] + Project SubAB [parent is B] + Project SubAC [parent is C] Project B (no modules) Project C (no modules) 2. The maven-remote-resources-plugin can help share resources (configuration files etc) between modules: http://maven.apache.org/plugins/maven-remote-resources-plugin/examples/sharing-resources.html 3. Look into the import scope (but this really only helps managing dependencies, not necessarily useful to you): http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies I don't know if any of these will help you but they are good things to know. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Different behavior when building a project as a module or stand-alone
My project has a basic multi-module structure, like this : The thing is, I get two different results for executing /mvn clean package/, whether I run it from /project-core/ or from /project/. *From project-core* *From project* Just an FYI. No one on the mailing list saw parts of what you posted, probably because Nabble ate the XML or because this mailing list does not support attachments. Convert your email to 100% plain text and try again. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Different behavior when building a project as a module or stand-alone
And indeed, the .jar is empty (safe a couple of metadata files), which cause the build to fail on /project-web/, which depends on /project-core/ Generally this should just work no matter where you have started your build. If it isn't working, that usually suggests you have configured something improperly in a pom somewhere. Is your source code in src/main/java as it should be? Or are you doing something funky with sourceDirectory that might involve ..? In short, what does your pom file for the project-core look like? Post it to pastebin or gist and send a link here. Perhaps also post the help:effective-pom output. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Check in of pom.xmls in multi module Maven project using scm:checkin
I used the maven release plugin to update the parent version numbers in my multi-module project (the modules are defined in different profiles) . Using profiles to turn on/off modules is generally not a good idea IMO. Why are you doing this? Now I want to check-in all these files using the maven scm:checkin command. I am using Clearcase as the SCM. I configured the plugin as below (image attached) in my parent pom: Images and other attachments are stripped when sent to this list. But this checks in only the parent pom. All the other pom.xmls in the modules remain checked out. Probably the other modules aren't active due to the profiles. Try removing the profiles entirely (just put the modules directly in the parent) and see if that works. The parent of the modules 1,2,3,4 is the parent project in the folder2. This is a non-standard project layout. Why would you do this? Can you not just move things around to conform to the norms, at least long enough to see if your problems are resolved? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Getting Error in Maven
Hi,
I am using maven 3.0.4 on my windows 7 machine, while running mvn
jetty:run, I am facing these errors, please provide with some solution.
Apache Maven 3.0.4 (r1232337; 2012-01-17 14:14:56+0530)
Maven home: D:\softwares\apache-maven-3.0.4
Java version: 1.7.0, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: x86, family: windows
[INFO] Error stacktraces are turned on.
[DEBUG] Reading global settings from
D:\softwares\apache-maven-3.0.4\conf\settings.xml
[DEBUG] Reading user settings from C:\Users\deb\.m2\settings.xml
[DEBUG] Using local repository at C:\Users\deb\.m2\repository
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for
C:\Users\deb\.m2\repository
[INFO] Scanning for projects...
[DEBUG] Extension realms for project
com.mycompany:myproject:war:1.0-SNAPSHOT: (none)
[DEBUG] Looking up lifecyle mappings for packaging war from
ClassRealm[plexus.core, parent: null]
[DEBUG] Resolving plugin prefix jetty from [org.apache.maven.plugins,
org.codehaus.mojo]
[DEBUG] Resolved plugin prefix jetty to
org.mortbay.jetty:maven-jetty-plugin from POM
com.mycompany:myproject:war:1.0-SNAPSHOT
[DEBUG] === REACTOR BUILD PLAN
[DEBUG] Project: com.mycompany:myproject:war:1.0-SNAPSHOT
[DEBUG] Tasks: [jetty:run]
[DEBUG] Style: Regular
[DEBUG]
===
[INFO]
[INFO]
[INFO] Building AppFuse Struts 2 Application 1.0-SNAPSHOT
[INFO]
[DEBUG] Resolving plugin prefix jetty from [org.apache.maven.plugins,
org.codehaus.mojo]
[DEBUG] Resolved plugin prefix jetty to
org.mortbay.jetty:maven-jetty-plugin from POM
com.mycompany:myproject:war:1.0-SNAPSHOT
[DEBUG] Lifecycle default - [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] === PROJECT BUILD PLAN
[DEBUG] Project: com.mycompany:myproject:1.0-SNAPSHOT
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): [runtime]
[DEBUG] Repositories (dependencies): [appfuse-snapshots (
http://oss.sonatype.org/content/repositories/appfuse-snapshots, snapshots),
central (http://repo.maven.apache.org/maven2, releases)]
[DEBUG] Repositories (plugins) : [appfuse-snapshots (
http://oss.sonatype.org/content/repositories/appfuse-snapshots, snapshots),
central (http://repo.maven.apache.org/maven2, releases)]
[DEBUG] --- init fork of com.mycompany:myproject:1.0-SNAPSHOT for
org.mortbay.jetty:maven-jetty-plugin:6.1.26:run (default-cli) ---
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): [compile, test]
[DEBUG]
---
[DEBUG] Goal:
org.codehaus.mojo:native2ascii-maven-plugin:1.0-alpha-1:native2ascii
(native2ascii-utf8)
[DEBUG] Style: Regular
[DEBUG] Configuration: ?xml version=1.0 encoding=UTF-8?
configuration
dest
default-value=${project.build.directory}/native2asciitarget/resources/dest
encodingUTF8/encoding
excludesApplicationResources.properties,
ApplicationResources_de*.properties,
ApplicationResources_fr*.properties,
ApplicationResources_nl*.properties,
Re: Getting Error in Maven
I am using maven 3.0.4 on my windows 7 machine, while running mvn jetty:run, I am facing these errors, please provide with some solution. In the future, DO NOT post your entire build debug log to this mailing list. Instead, pull out the handful of lines that say ERROR and only send them. Alternatively, you can post the whole debug to Gist or Pastebin and send a link here. [ERROR] Failed to execute goal org.codehaus.mojo:native2ascii-maven-plugin:1.0-alpha-1:native2ascii (native2ascii-utf8) on project myproject: Execution native2ascii-utf8 of goal org.codehaus.mojo:native2ascii-maven-plugin:1.0-alpha-1:native2ascii failed: Error starting Sun's native2ascii: sun.tools.native2ascii.Main - I have no idea why native2ascii is not working, but this is your problem. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Getting Error in Maven
From the output it can be seen Apache Maven 3.0.4 (r1232337; 2012-01-17 14:14:56+0530) . vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0\jre ... That is, Maven's using C:\Program Files\Java\jdk1.7.0\jre as your JAVA_HOME which instead should be your JDK folder -Original Message- From: debashish mukherjee [mailto:deba...@gmail.com] Sent: March-30-12 6:39 AM To: users@maven.apache.org Subject: Getting Error in Maven Hi, I am using maven 3.0.4 on my windows 7 machine, while running mvn jetty:run, I am facing these errors, please provide with some solution. Apache Maven 3.0.4 (r1232337; 2012-01-17 14:14:56+0530) Maven home: D:\softwares\apache-maven-3.0.4 Java version: 1.7.0, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows 7, version: 6.1, arch: x86, family: windows [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from D:\softwares\apache-maven-3.0.4\conf\settings.xml [DEBUG] Reading user settings from C:\Users\deb\.m2\settings.xml [DEBUG] Using local repository at C:\Users\deb\.m2\repository [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for C:\Users\deb\.m2\repository [INFO] Scanning for projects... [DEBUG] Extension realms for project com.mycompany:myproject:war:1.0-SNAPSHOT: (none) [DEBUG] Looking up lifecyle mappings for packaging war from ClassRealm[plexus.core, parent: null] [DEBUG] Resolving plugin prefix jetty from [org.apache.maven.plugins, org.codehaus.mojo] [DEBUG] Resolved plugin prefix jetty to org.mortbay.jetty:maven-jetty-plugin from POM com.mycompany:myproject:war:1.0-SNAPSHOT [DEBUG] === REACTOR BUILD PLAN [DEBUG] Project: com.mycompany:myproject:war:1.0-SNAPSHOT [DEBUG] Tasks: [jetty:run] [DEBUG] Style: Regular [DEBUG] === [INFO] [INFO] [INFO] Building AppFuse Struts 2 Application 1.0-SNAPSHOT [INFO] [DEBUG] Resolving plugin prefix jetty from [org.apache.maven.plugins, org.codehaus.mojo] [DEBUG] Resolved plugin prefix jetty to org.mortbay.jetty:maven-jetty-plugin from POM com.mycompany:myproject:war:1.0-SNAPSHOT [DEBUG] Lifecycle default - [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] [DEBUG] Lifecycle clean - [pre-clean, clean, post-clean] [DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy] [DEBUG] Lifecycle default - [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] [DEBUG] Lifecycle clean - [pre-clean, clean, post-clean] [DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy] [DEBUG] Lifecycle default - [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] [DEBUG] Lifecycle clean - [pre-clean, clean, post-clean] [DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy] [DEBUG] === PROJECT BUILD PLAN [DEBUG] Project: com.mycompany:myproject:1.0-SNAPSHOT [DEBUG] Dependencies (collect): [] [DEBUG] Dependencies (resolve): [runtime] [DEBUG] Repositories (dependencies): [appfuse-snapshots ( http://oss.sonatype.org/content/repositories/appfuse-snapshots, snapshots), central (http://repo.maven.apache.org/maven2, releases)] [DEBUG] Repositories (plugins) : [appfuse-snapshots ( http://oss.sonatype.org/content/repositories/appfuse-snapshots, snapshots), central (http://repo.maven.apache.org/maven2, releases)] [DEBUG] --- init fork of com.mycompany:myproject:1.0-SNAPSHOT for org.mortbay.jetty:maven-jetty-plugin:6.1.26:run (default-cli) --- [DEBUG] Dependencies (collect): [] [DEBUG] Dependencies (resolve): [compile, test] [DEBUG] --- [DEBUG] Goal:
Re: Getting Error in Maven
You are using native2ascii-maven-plugin:1.0-alpha-1 with Java version:
1.7.0 and 1.0-alpha-1 version of plugin is not compatible with JDK 7.
So you either upgrade plugin to version 1.0-beta-1 or run Maven with JDK 6
Markku
On 30.3.2012 16:39, debashish mukherjee wrote:
Hi,
I am using maven 3.0.4 on my windows 7 machine, while running mvn
jetty:run, I am facing these errors, please provide with some solution.
Apache Maven 3.0.4 (r1232337; 2012-01-17 14:14:56+0530)
Maven home: D:\softwares\apache-maven-3.0.4
Java version: 1.7.0, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: x86, family: windows
[INFO] Error stacktraces are turned on.
[DEBUG] Reading global settings from
D:\softwares\apache-maven-3.0.4\conf\settings.xml
[DEBUG] Reading user settings from C:\Users\deb\.m2\settings.xml
[DEBUG] Using local repository at C:\Users\deb\.m2\repository
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for
C:\Users\deb\.m2\repository
[INFO] Scanning for projects...
[DEBUG] Extension realms for project
com.mycompany:myproject:war:1.0-SNAPSHOT: (none)
[DEBUG] Looking up lifecyle mappings for packaging war from
ClassRealm[plexus.core, parent: null]
[DEBUG] Resolving plugin prefix jetty from [org.apache.maven.plugins,
org.codehaus.mojo]
[DEBUG] Resolved plugin prefix jetty to
org.mortbay.jetty:maven-jetty-plugin from POM
com.mycompany:myproject:war:1.0-SNAPSHOT
[DEBUG] === REACTOR BUILD PLAN
[DEBUG] Project: com.mycompany:myproject:war:1.0-SNAPSHOT
[DEBUG] Tasks: [jetty:run]
[DEBUG] Style: Regular
[DEBUG]
===
[INFO]
[INFO]
[INFO] Building AppFuse Struts 2 Application 1.0-SNAPSHOT
[INFO]
[DEBUG] Resolving plugin prefix jetty from [org.apache.maven.plugins,
org.codehaus.mojo]
[DEBUG] Resolved plugin prefix jetty to
org.mortbay.jetty:maven-jetty-plugin from POM
com.mycompany:myproject:war:1.0-SNAPSHOT
[DEBUG] Lifecycle default - [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] === PROJECT BUILD PLAN
[DEBUG] Project: com.mycompany:myproject:1.0-SNAPSHOT
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): [runtime]
[DEBUG] Repositories (dependencies): [appfuse-snapshots (
http://oss.sonatype.org/content/repositories/appfuse-snapshots, snapshots),
central (http://repo.maven.apache.org/maven2, releases)]
[DEBUG] Repositories (plugins) : [appfuse-snapshots (
http://oss.sonatype.org/content/repositories/appfuse-snapshots, snapshots),
central (http://repo.maven.apache.org/maven2, releases)]
[DEBUG] --- init fork of com.mycompany:myproject:1.0-SNAPSHOT for
org.mortbay.jetty:maven-jetty-plugin:6.1.26:run (default-cli) ---
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): [compile, test]
[DEBUG]
---
[DEBUG] Goal:
org.codehaus.mojo:native2ascii-maven-plugin:1.0-alpha-1:native2ascii
(native2ascii-utf8)
[DEBUG] Style: Regular
[DEBUG] Configuration:?xml version=1.0 encoding=UTF-8?
configuration
dest
default-value=${project.build.directory}/native2asciitarget/resources/dest
Re: How to Add multiple Jars
I have realized a complete pom structure for kk 4.0.1 and i'm porting it now to 6.0.0. I whish have a spring storefront. Maybe we can share can't we? I think I'll post my work as soon I finish the demo a admin packaging. -- View this message in context: http://maven.40175.n5.nabble.com/How-to-Add-multiple-Jars-tp5579644p5607803.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Unable to update index for central|http://repo1.maven.org/maven2
hello,these days,I try many ways to update index for central(http://repo1.maven.org/maven2 ),but,all failure.Can you tell me the reason and how to sovle this problem,thank you very mach. zhangwujun --- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. ---
RE: Unable to update index for central|http://repo1.maven.org/maven2
Hi, Pls check the network connection using ping repo1.maven.org Maybe there are some changes in your network. If the result of ping is failure, you need add a proxy in your settgins.xml. Br, Tim -Original Message- From: zhangwujun [mailto:zhangwu...@neusoft.com] Sent: Saturday, March 31, 2012 10:07 AM To: users Subject: Unable to update index for central|http://repo1.maven.org/maven2 hello,these days,I try many ways to update index for central(http://repo1.maven.org/maven2 ),but,all failure.Can you tell me the reason and how to sovle this problem,thank you very mach. zhangwujun --- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
