Re: Error running Maven
Wheter you are connected through a WIFI connection or a wired connection should not make a difference. Poxy settings should be set if you need to go through a proxy server to access internet. Otherwise don't put anything in it. I believe you are confusing a proxy server with a wifi access point which are two very different things. Cheers, Guillaume Le 6/04/2012 14:18, nanosoft a écrit : I have installed maven in C:\apache-maven-3.0.4-bin. Its installed successfully as mvn --version gives expected o/p. I have wifi internet connection for which I have changed proxy settings in conf/settings.xml to following: proxies proxy idoptional/id activetrue/active protocolhttp/protocol usernamesanp/username passwordpwd/password host/host port80/port nonProxyHostslocalhost/nonProxyHosts /proxy /proxies Here sanp is the name of wifi connection I connect and pwd is the password. In IE under tools-internet options-connections-lan settings no proxy address is defined so i have lefthost tag empty. Other parts of settings.xml is untouched. when I execute below command I get error : *C:\Maven Workspacesmvn archetype:generate -DgroupId=com.mycompany.app -Dartifac tId=my-app -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=fa lse -eX* [INFO] Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1.676s [INFO] Finished at: Fri Apr 06 17:04:53 IST 2012 [INFO] Final Memory: 3M/245M [INFO] [ERROR] The goal you specified requires a project to execute but there is no POM in this directory (C:\Maven Workspaces). Please verify you invoked Maven from t he correct directory. - [Help 1] org.apache.maven.lifecycle.MissingProjectException: The goal you specified requi res a project to execute but there is no POM in this directory (C:\Maven Workspa ces). Please verify you invoked Maven from the correct directory. at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl eStarter.java:89) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun cher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav a:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La uncher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java: 352) [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please rea d the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProject Exception C:\Maven Workspaces Please help what should i do? -- View this message in context: http://maven.40175.n5.nabble.com/Error-running-Maven-tp5622633p5622633.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven concurrent builds
Dear all, I was having some doubts regarding Maven's ability to handle properly concurrent builds. Lately, I had several builds of our project that failed and it seemed that it was due to interferences between concurrent builds of the same version of the same project. I have a jenkins server which have 6 different builds: * 1 for continuous build (which runs tests but does not deploy the artifacts) * 1 for nightly build * 1 for releases (or almost release, ie, the pom is still in SNAPSHOT version but could become a release) All this is multiplied by two, because I have two versions (on 2 different branches). So I had 2 questions: 1. Can/Does Maven support concurrent builds of the same version of the same project? If yes, do I need to do something to achieve this? If not, is it something that Maven developers are considering? 2. Can/Does Maven support concurrent builds of different versions of the same project? Cheers, Guillaume - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven concurrent builds
OK, good to know. Somehow, I always assumed that Maven was actually
handling concurrency safely.
Too bad that we have to waste extra space to handle this, but at least
there are easy workarounds.
Cheers
Guillaume
Le 7/03/2012 11:41, Srinath C a écrit :
Always use a different local repositories for different projects in Jenkins.
You can do this by setting the system property
-Dmaven.local.repo={project_workspace_dir}
Regards,
Srinath.
On Wed, Mar 7, 2012 at 1:59 PM, Jörg Schaible
joerg.schai...@scalaris.comwrote:
Hi Guillaume,
Guillaume Polet wrote:
Dear all,
I was having some doubts regarding Maven's ability to handle properly
concurrent builds. Lately, I had several builds of our project that
failed and it seemed that it was due to interferences between concurrent
builds of the same version of the same project.
I have a jenkins server which have 6 different builds:
* 1 for continuous build (which runs tests but does not deploy the
artifacts)
* 1 for nightly build
* 1 for releases (or almost release, ie, the pom is still in SNAPSHOT
version but could become a release)
All this is multiplied by two, because I have two versions (on 2
different branches).
So I had 2 questions:
1. Can/Does Maven support concurrent builds of the same version of the
same project?
Not out of the box. Since by default both builds will use the same local
repository creating the same artifacts at same time, the artifacts in the
repository are likely to be corrupted.
If yes, do I need to do something to achieve this?
Use separate local repositories, it can be defined using separate
settings.xml files or by call with a system property. Actually I don't know
if Jenkins already supports something like this, because it's a general
problem, see below.
If not,
is it something that Maven developers are considering?
It's not the first time this problem has been risen.
2. Can/Does Maven support concurrent builds of different versions of the
same project?
They may still corrupt the metadata.xml files, but it is less likely and
has
AFAICS less consequences.
However, every concurrent build may corrupt a shared local repository,
because both builds may download the same artifacts at same time. A
scenario
where this might happen is when you upgrade versions (e.g. of plugins) in a
common master-pom and start two parallel builds then. Actually I am not
sure
if you're safe when running one Maven build in parallel mode. A repository
manager like Nexus might prevent this scenario by detecting the same
request, but again I am not sure if it does.
BTW: This is also the reason why you should never share a local repository
with a network mount by multiple users.
Cheers,
Guillaume
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven concurrent builds
Le 7/03/2012 13:52, Jörg Schaible a écrit : Guillaume Polet wrote: OK, good to know. Somehow, I always assumed that Maven was actually handling concurrency safely. Too bad that we have to waste extra space to handle this, but at least there are easy workarounds. If you use a repository manager in your intranet, you may simple wipe the local repo every time. Yes but then my builds takes longer to perform because it needs to download again all dependencies (and there are quite a few) plus all the required plugins. Thanks for all your comments, I learned something today? Cheers, Guillaume - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven concurrent builds
Yeah, I just found out about this but it is in an advanced hidden by
default panel. I checked it for all my builds that could interfere with
each other. Seems kind of strange that this is not more obvious as not
checking it results unpredictable behaviour.
Sorry to the ML-users as this is getting of Maven and more on Jenkins. I
won't continue on the subject.
Thanks to everyone who answered, it really solved my issues.
Cheers,
Guillaume
Le 7/03/2012 16:24, Michael Haefele a écrit :
Jenkins also has a setting Use private Maven repository in the build
section of the job configuration which takes care of this for you.
Mike
On Wed, Mar 7, 2012 at 5:41 AM, Srinath Csrinat...@gmail.com wrote:
Always use a different local repositories for different projects in Jenkins.
You can do this by setting the system property
-Dmaven.local.repo={project_workspace_dir}
Regards,
Srinath.
On Wed, Mar 7, 2012 at 1:59 PM, Jörg Schaible
joerg.schai...@scalaris.comwrote:
Hi Guillaume,
Guillaume Polet wrote:
Dear all,
I was having some doubts regarding Maven's ability to handle properly
concurrent builds. Lately, I had several builds of our project that
failed and it seemed that it was due to interferences between concurrent
builds of the same version of the same project.
I have a jenkins server which have 6 different builds:
* 1 for continuous build (which runs tests but does not deploy the
artifacts)
* 1 for nightly build
* 1 for releases (or almost release, ie, the pom is still in SNAPSHOT
version but could become a release)
All this is multiplied by two, because I have two versions (on 2
different branches).
So I had 2 questions:
1. Can/Does Maven support concurrent builds of the same version of the
same project?
Not out of the box. Since by default both builds will use the same local
repository creating the same artifacts at same time, the artifacts in the
repository are likely to be corrupted.
If yes, do I need to do something to achieve this?
Use separate local repositories, it can be defined using separate
settings.xml files or by call with a system property. Actually I don't know
if Jenkins already supports something like this, because it's a general
problem, see below.
If not,
is it something that Maven developers are considering?
It's not the first time this problem has been risen.
2. Can/Does Maven support concurrent builds of different versions of the
same project?
They may still corrupt the metadata.xml files, but it is less likely and
has
AFAICS less consequences.
However, every concurrent build may corrupt a shared local repository,
because both builds may download the same artifacts at same time. A
scenario
where this might happen is when you upgrade versions (e.g. of plugins) in a
common master-pom and start two parallel builds then. Actually I am not
sure
if you're safe when running one Maven build in parallel mode. A repository
manager like Nexus might prevent this scenario by detecting the same
request, but again I am not sure if it does.
BTW: This is also the reason why you should never share a local repository
with a network mount by multiple users.
Cheers,
Guillaume
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Quick Artifact Question
Maven has no issues with zip files as far as I know (I attach some create by maven-assembly everyday) . Maybe did you forgot to attach it to the build? I believe maven-build-helper can help you on that. Cheers, Guillaume Le 9/02/2012 16:09, Stephen Wenner a écrit : At the end of my build process, I have created a plugin to modify some files in my work-space and then zip it up into afilename.zip. The problem I'm having is that Maven doesn't seem to recognize .zip files as deployable artifacts. How do I change this? I'm running on Jenkins Maven 3.0.3 Artifactory Thanks in advance. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: No reattempt to resolve broken released artifacts
Hello, have a look at updatePolicy: http://maven.apache.org/settings.html#Repositories Cheers, Guillaume Le 30/01/2012 14:21, frank.ja...@tolina.de a écrit : Hello, we shortly switched our company's infrastructure to maven and are now experiencing a strange behaviour of dependency resolution. Say my.project:1.0.0 requires my.cool.component:jar:3.7.0 and I try to build my.project:1.0.0 before the dependency was deployed to my central repository, my local repository ends up having the folder structure of my/cool/component/3.7.0 with two files in it, namely my.cool.component.jar.lastUpdated and my.cool.component.pom.lastUpdated. The build fails, which is perfectly correct. Afterwards, my.cool.component:jar:3.7.0 is deployed to central repo, but my local repo never gets the jar, so I always have to clean my local repo manually, before I can get the build of my.project:1.0.0 working. Is this by design or simply a bug? Regards Frank - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Make Source directory the Destination directory
I am not sure that I understand correctly what you are trying to do (mainly because I have never used that plugin), but have you looked at the goal documentation?: http://maven-samaxes-plugin.googlecode.com/svn/sites/maven-minify-plugin/minify-mojo.html, there is a cssTargetDir and jsTargetDir configuration option. Now maybe you could explain the purpose of generating those minified files directly into your source directory? There may be a cleaner/simpler way to do what you actually attempt to perform. Cheers, Guillaume Le 24/01/2012 18:27, ibbignerd a écrit : I am new to using maven, but understand a little. I need to create a pom file that makes the destination of a minified file be where the source file is. here is a snippet of my code plugins plugin groupIdcom.samaxes.maven/groupId artifactIdmaven-minify-plugin/artifactId version1.3.5/version executions execution iddefault-minify/id phaseprocess-resources/phase configuration cssSourceDircss/cssSourceDir cssSourceFiles cssSourceFilesrc/main/**/*.css/cssSourceFile /cssSourceFiles cssFinalFilestyle.css/cssFinalFile jsSourceDirjs/jsSourceDir jsSourceFiles jsSourceFiletablefilter.js/jsSourceFile /jsSourceFiles jsFinalFilescript.js/jsFinalFile /configuration goals goalminify/goal /goals /execution /executions /plugin /plugins I also need it to search for all js and css files in the subfolders. Please let me know if you guys need any more info. Thanks -- View this message in context: http://maven.40175.n5.nabble.com/Make-Source-directory-the-Destination-directory-tp5323988p5323988.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Installation glitch!
Have you looked at the archive of this thread? Here is a copy of my answer: Looks like mvn is not on your path (the purpose of step 2 thru 7 is to have, one way or another, the bin directory of Maven in your path variable). Note that after updating the environment variables you should open a new terminal and not reuse an existing one. If that is not your problem, could you post the output of the command set (just type 'set' without the single quotes in a terminal). Cheers, Guillaume Le 23/01/2012 09:04, igorm a écrit : I am having the same problem. I checked all steps another time. Do all variables have to be in the Users category? mvn -version is not being recognized as a command. If anyone could help, would be much appreciated. - Igor -- View this message in context: http://maven.40175.n5.nabble.com/Installation-glitch-tp5130974p5165461.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: Installation glitch!
Hi Igor, I guess that your installation is located here, then: C:\Program Files\Apache Software Foundation\apache-maven-3.0.3\bin I suppose that the line returns and other strange split are due to the Windows-terminal (it sucks, I know. A way around this is to type 'set set.txt' which will output everything to a set.txt file and then open that file). Have you checked opening the Terminal to that precise location and type 'mvn -version' directly there. Have you looked for a typo somewhere? Could it be that you installed Maven in the 'Program files (x86)' folder instead of the default 'Program Files'? (That is a big difference with WinXP). Whitespaces could be an issue, although it should work (you can try java -version, it work). Some users suggested to install maven in a path without whitespaces (like c:\Users\Maven). Of course, this requires to change the path environment variable accordingly. Other users suggested simply restarting the computer, but I have some doubts about this. Normally, terminals/shells are initiated with their default environment variables and it is cached in the terminal, meaning that changes made afterwards are not directly taken into account, but if you re-open one you get the latest set values. Let us know your findings. Cheers, Guillaume Le 23/01/2012 21:20, igorm a écrit : C:\Program Files\Apache Software Foundation\apache-maven-3.0.3\b in - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Single zip out of multi module project
Have a look at the maven assembly plugin. Cheers, Guillaume Le 21/01/2012 10:54, vijayrcse a écrit : Hi I am a newbie to Maven. This is my problem I have a multi module pom project. Ex : A is the parent having its pom, with 3 sub modules as B, C D When i build A i am getting three separate zip files for B c and D How to build A such that i just get one zip, and i should be able to unzip and deploy it as three deployment with in a same location Thanks in Advance -vijay -- View this message in context: http://maven.40175.n5.nabble.com/Single-zip-out-of-multi-module-project-tp5162415p5162415.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mavem-war-plugin packagingExcludes regex not working
Isn't that what I told you? Cheers, Guillaume Le 20/01/2012 12:41, mschipperheyn a écrit : .*(?!min)\.js does the trick. Why didn't I find this sooner?lt;smiley image=quot;anim_confused.gifquot;/ -- View this message in context: http://maven.40175.n5.nabble.com/mavem-war-plugin-packagingExcludes-regex-not-working-tp5139981p5160145.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skipping the TAR packaging step
Hi,
from what you provide us, I think that you are using the predefined
descriptor 'project' of maven assembly plugin which produces by default
a zip, a tar.gz and a tar.bz2 file
(http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html).
Now, if you want a single big fat jar containing all the classes, just
switch to the descriptor 'jar-with-dependencies' which will unpack all
the jar you depend on and recreate a big jar file containing all the
unpacked classes, plus, the ones of your current project.
Now, if you want to keep those three files (zip, tar.gz and tar.bz2) but
you want to have 2 different kind of builds:
* one that produces the jar file of the current project
* one that produces everything as now
You have two options:
1) you create 2 profiles, one that contains the maven assembly plugin
and another one without it.
2) you bind the assembly plugin to a phase which is after the phase
package (for example, verify), and in the first case you only call
'mvn package' and the second one you call 'mvn verify'
If what you want is to have a build with:
* one that produces the big fat jar file
* one that produces everything as now
Your only choice is to use profile and configure the maven assembly
plugin differently in each profile.
If you look for information on profiles, go here:
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
If you look for information on lifecylce, phases, etc..., go here:
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
Be careful with profiles because, as mentioned on the maven site, there
are several pitfalls to profiles.
Cheers,
Guillaume
Le 18/01/2012 12:52, jackett_dad a écrit :
Wayne,
Thanks for the reply.
I am the resident expert with Maven, so I am the only help I have. If we
had someone like you are describing, I would very happy indeed. So far
though, things are looking good, but it's like walking through the dark with
a flashlight.
As for the other formats, I'm not looking to get rid of them forever, only
in the iterative development cycle where I compile, deploy and test upwards
to 20 times a day. The jar is all I need in this situation.
The old build was done exclusively with Ant.
My guess about why I'm generating so many different deployment artifacts is
that it is due to the assembly plugin in my project pom:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version${maven.assembly.plugin.version}/version
executions
execution
idcreate-project-bundle/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
descriptorRefs
descriptorRefproject/descriptorRef
/descriptorRefs
/configuration
/execution
/executions
/plugin
Is there a way to configure this to only generate the jar? If I am to use
the shade plugin, how do I configure it to indicate the suppression I'm
looking for? I read the usage page for both plugins but haven't found what
I'm looking for (though I admit I could easily have missed it).
Thanks,
Scott
--
View this message in context:
http://maven.40175.n5.nabble.com/Skipping-the-TAR-packaging-step-tp5152958p5154628.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: mavem-war-plugin packagingExcludes regex not working
Test Results Regular Expression Original Expression (?!min)\.js as a Java string(?!min)\\.js Replacement groupCount()0 Test Target String matches() replaceFirst() replaceAll() lookingAt() find() group(0) 1 /msa-network/msa-network-min.js No /msa-network/msa-network-min.js /msa-network/msa-network-min.js No No 2 /msa-network/msa-network.js No /msa-network/msa-network /msa-network/msa-network No Yes .js It obviously does not work... See column matches() Maybe you meant this: .*?(?!min)\.js Cheers, Guillaume Le 13/01/2012 13:32, mschipperheyn a écrit : Sorry, try it here http://www.regexplanet.com/simple/index.html -- View this message in context: http://maven.40175.n5.nabble.com/mavem-war-plugin-packagingExcludes-regex-not-working-tp5139981p5142437.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: Help with installing a non-maven jar in local repo .
What you are trying to do does not seem possible (at least the first time). Remove the dependency first, then do the install, then re-add the dependency. And you are good to go, but this is really against all good practices. Cheers, Guillaume Le 13/01/2012 14:03, vvkbtnkr a écrit : I am aware of the repo manager concept, but setting it up is more work than what I want for the quick-fire poc that I am working on, would be reaally helpful if some one can point out the mistake in the pom snippet posted earlier and help me fix that ... -- View this message in context: http://maven-users.828.n2.nabble.com/Help-with-installing-a-non-maven-jar-in-local-repo-tp7182923p7183920.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Disabling Profiles during release
Not sure this is the right place to put your question and not sure I understand what's your question exactly. Yes it is possible to deactivate profiles. As for jenkins, in the goals and options box, just put: -P !profile1,!profile2 Have you tried running mvn from the command line? If yes, then your problem needs to be answered here. Otherwise, I would ask jenkins guys. Cheers, Guillaume Le 13/01/2012 15:09, Asmann, Roland a écrit : Hi all, I have this company-wide POM that has several profiles that are activated when running on Jenkins. Now during the normal build of this POM, I tell Jenkins to deactivate several profiles, because they just can't run. Today I needed to make a release of this POM, and I tried to deactivate the profiles as well -- using -Darguments=-P!profile1,!profile2 etc. This does not seem to work however, so I am now unable to release this POM using Jenkins! Before, when I had to activate profiles, this worked just fine! Is it just not possible to deactivate profiles or am I missing something here? Thanks, - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to run a maven goal when there is tests failures?
Although I did see your answer, I did not understand how failsafe was resolving the problem, I do now. Cheers, Guillaume Le 10/01/2012 19:19, Stephen Connolly a écrit : given that nobody else bothered to read the original question, it does not surprise me that nobody bothered to read my original answer of using failsafe ;-) - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 10 Jan 2012 18:16, Stephen Connollystephen.alan.conno...@gmail.com wrote: use failsafe. parse the failsafe results yourself... if they show a test failure, do your special thing then let failsafe verify stop the build - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 10 Jan 2012 16:58, Xavier S.xavier.seign...@gmail.com wrote: Thanks Guillaume! That's exactly what I want to do. So people, any idea? Regards, Xavier 2012/1/10 Guillaume Poletguillaume.po...@gmail.com Tell me if I am wrong Xavier, but I think that what he would like to do is perform something special when the tests fail, not just skip them or not fail the build. My guess would be that he is expecting some kind of on failure/on tests failure phase where he could attach other maven plugins to perform alternate behaviour. Unfortunately I have no idea on how this could be done. Probably using Ant or by writing your own plugin, but I find both solutions quite poor. Maybe Maven is not the tool to be used to perform this. Although you can do a lot of things with Maven, sometimes bending its original objectives too far away is just cumbersome and counter-productive /(not sure this english, btw). /Cheers, Guillaume Le 10/01/2012 17:22, Jeff MAURY a écrit : what about http://maven.apache.org/**plugins/maven-surefire-plugin/**test-mojo.html# **testFailureIgnore http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#testFailureIgnore Jeff MAURY On Tue, Jan 10, 2012 at 4:55 PM, Xavier S.xavier.seign...@gmail.com ** wrote: Thanks for all your answers, but I think I should re explain my need. I don't want to skip the tests. The default fail fast mode of maven suits me (section 6.1.8 http://www.sonatype.com/books/**mvnref-book/reference/running-** sect-options.html http://www.sonatype.com/books/mvnref-book/reference/running-sect-options.html ). I just want to run my custom mojo just after my tests failures and just before the end of the maven execution (if there is build failures, maven do not even finishes the current test phase). Regards, Xavier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Howto access project version programmatically within application
Just google org/apache/maven/execution/DefaultRuntimeInformation.java . http://grepcode.com/file/repo1.maven.org/maven2/org.apache.maven/maven-core/2.0.5/org/apache/maven/execution/DefaultRuntimeInformation.java?av=h Cheers, Guillaume Le 11/01/2012 15:03, Steve Cohen a écrit : A solution to this question appears to have been offered here, in 2007. http://maven.40175.n5.nabble.com/HowTo-access-project-version-programmatically-in-application-td82542.html It references a page explaining how to do it. That page is now gone: http://svn.apache.org/repos/asf/maven/components/trunk/maven-core/src/main/java/org/apache/maven/execution/DefaultRuntimeInformation.java Does this page or another more advanced way to do this now exist? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to run a maven goal when there is tests failures?
Tell me if I am wrong Xavier, but I think that what he would like to do is perform something special when the tests fail, not just skip them or not fail the build. My guess would be that he is expecting some kind of on failure/on tests failure phase where he could attach other maven plugins to perform alternate behaviour. Unfortunately I have no idea on how this could be done. Probably using Ant or by writing your own plugin, but I find both solutions quite poor. Maybe Maven is not the tool to be used to perform this. Although you can do a lot of things with Maven, sometimes bending its original objectives too far away is just cumbersome and counter-productive /(not sure this english, btw). /Cheers, Guillaume Le 10/01/2012 17:22, Jeff MAURY a écrit : what about http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#testFailureIgnore Jeff MAURY On Tue, Jan 10, 2012 at 4:55 PM, Xavier S.xavier.seign...@gmail.comwrote: Thanks for all your answers, but I think I should re explain my need. I don't want to skip the tests. The default fail fast mode of maven suits me (section 6.1.8 http://www.sonatype.com/books/mvnref-book/reference/running-sect-options.html ). I just want to run my custom mojo just after my tests failures and just before the end of the maven execution (if there is build failures, maven do not even finishes the current test phase). Regards, Xavier
Re: Installation glitch!
Looks like mvn is not on your path (the purpose of step 2 thru 7 is to have, one way or another, the bin directory of Maven in your path variable). Note that after updating the environment variables you should open a new terminal and not reuse an existing one. If that is not your problem, could you post the output of the command set (just type 'set' without the single quotes in a terminal). Cheers, Guillaume Le 9/01/2012 11:15, MH a écrit : Hi I am a first time user of maven and new to open source in general. I have downloaded the latest version .bin file and followed the instructions “copied and pasted” below: Windows 2000/XP 1.. Unzip the distribution archive, i.e. apache-maven-3.0.3-bin.zip to the directory you wish to install Maven 3.0.3. These instructions assume you chose C:\Program Files\Apache Software Foundation. The subdirectory apache-maven-3.0.3 will be created from the archive. 2.. Add the M2_HOME environment variable by opening up the system properties (WinKey + Pause), selecting the Advanced tab, and the Environment Variables button, then adding the M2_HOME variable in the user variables with the value C:\Program Files\Apache Software Foundation\apache-maven-3.0.3. Be sure to omit any quotation marks around the path even if it contains spaces. Note: For Maven 2.0.9, also be sure that the M2_HOME doesn't have a '\' as last character. 3.. In the same dialog, add the M2 environment variable in the user variables with the value %M2_HOME%\bin. 4.. Optional: In the same dialog, add the MAVEN_OPTS environment variable in the user variables to specify JVM properties, e.g. the value -Xms256m -Xmx512m. This environment variable can be used to supply extra options to Maven. 5.. In the same dialog, update/create the Path environment variable in the user variables and prepend the value %M2% to add Maven available in the command line. 6.. In the same dialog, make sure that JAVA_HOME exists in your user variables or in the system variables and it is set to the location of your JDK, e.g. C:\Program Files\Java\jdk1.5.0_02 and that %JAVA_HOME%\bin is in your Path environment variable. 7.. Open a new command prompt (Winkey + R then type cmd) and run mvn --version to verify that it is correctly installed. After running several different permutations and attempting to gain an expected response from the command prompt using mvn –version the system has proved to be not properly installed. The command mvn is not recognised. I have a standard Windows 7 install with a fairly standard AMD processor. Plenty of memory and disk space. Can anyone identify what might be causing this phenomenon on my machine? Many thanks Martin Harrison - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven / Java 1.7 compliance
He is running 1.7, since he gets an explicit message from the compiler
to use source 7 and he already posted the output of the mvn --version.
Have you tried the debug mode with -X to see what the maven compiler
does? Have you tried directly setting the properties to 1.7 in the
configuration instead of using properties (just for testing)? Also, you
could try dropping the configuration part (except the encoding) since
you are using the maven properties corresponding to that configuration.
Cheers,
Guillaume
Le 6/01/2012 09:52, Holger Hoffstaette a écrit :
On Fri, 06 Jan 2012 03:45:19 +0100, Johannes.Lichtenberger wrote:
On 01/06/2012 02:54 AM, Dave Wolf wrote:
Instead of 1.7 try simply 7.
Seems it doesn't have any impact. In Eclipse itself it doesn't seem to
change anything, too, but in Eclipse the build path is correct for all
projects. I just want to get `mvn` in the shell running after I've updated
the projects to Java 7 some time ago to double check if the unit tests are
working before commiting to the CI-Server (and to produce JARs).
I can compile JDK7 source just fine (using new 7-only classes etc., with
1.7 as source/target:
..
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version${compiler.plugin.version}/version
configuration
source1.7/source
target1.7/target
/configuration
/plugin
..
maven-compiler-plugin is 2.3.2.
Try mvn --version to verify that you are really using the correct JDK.
-h
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How to configure properties-maven-plugin to report built in properties/variables
You can achieve this very easily by using the maven-ant-plugin combined
with the echoproperties Ant task
(http://ant.apache.org/manual/Tasks/echoproperties.html).
Cheers,
Guillaume
Le 3/01/2012 17:22, David Hoffer a écrit :
How can I get project variables/properties exported to property file?
I'm using properties-maven-plugin and it's good but it only reports
things I have explicitly created as properties in my project. I need
to also get a report on things that maven already defined such as:
project...
scm
connectionscm:svn:https://.../connection
developerConnectionscm:svn:https://.../developerConnection
urlhttps://.../url
/scm
...
/project
To get these values reported using this plugin I have to add this to my project:
properties
project.scm.connection${project.scm.connection}/project.scm.connection
project.scm.developerConnection${project.scm.developerConnection}/project.scm.developerConnection
project.scm.url${project.scm.url}/project.scm.url
/properties
This is tedious and error prone. Is there a way to report this
without adding variables as properties manually?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: assembly plug-in config
Hi, not sure of what you are trying to achieve here but the documentation should help you: * http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html * http://maven.apache.org/plugins/maven-assembly-plugin/examples/index.html Cheers, Guillaume Le 3/01/2012 09:28, Prashant Neginahal a écrit : Hi, I am using assembly plug-in to create zip of multi-module project of below structure. parent1 --child-1 --child-2 pom.xml I would like to create the parent1.zip of same structure as below. parent1.zip --child-1 --child-2 pom.xml Could someone help what could be the assembly configuration for the same, please? Thanks, Prashant - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Unable to use maven-ant-tasks
If I add the following line to your script, it works smoothly (if the maven-ant-tasks jar is on ant classpath): typedef resource=org/apache/maven/artifact/ant/antlib.xml uri=antlib:org.apache.maven.artifact.ant/ Cheers, Guillaume Le 27/12/2011 01:41, Scott Shambarger a écrit : I'm new to ant and maven, so I'm sure this is a silly questionstill, I'm stuck. I'm using the rpm install of ant/maven/etc for Fedora 16. I'm trying to build a project that requires ant and maven, and uses maven-ant-tasks (I have maven-ant-tasks-2.1.1-8.fc16 installed), however, I always receive the following error: BUILD FAILED /opt/devel/test/build.xml:4: Problem: failed to create task or type antlib:org.apache.maven.artifact.ant:remoteRepository Cause: The name is undefined. I'm pretty sure I have some sort of configuration error, but after several hours crawling the examples and docs, I'm just not making any progress... I don't have CLASSPATH defined, and have tried using ant -noclasspath with the same results. I've linked the /usr/share/java/maven-ant-tasks.jar (from the rpm) into my ~/.ant/lib directory, and reduced the build.xml file to the following (this file uses the same syntax as the project I'm trying to build, and produces the same error): --- build.xml ?xml version=1.0 ? project name=Test default=help basedir=. xmlns:artifact=antlib:org.apache.maven.artifact.ant artifact:remoteRepository id=my.repository url=http://example.com; snapshots updatePolicy=always / /artifact:remoteRepository target name=help echo message=Test/ /target /project end build.xml This appears to follow the example on http://maven.apache.org/ant-tasks/installation.html which has the following: project ... xmlns:artifact=antlib:org.apache.maven.artifact.ant ... /project The output of ant -diagnostics are: --- Ant diagnostics report --- Apache Ant(TM) version 1.8.2 compiled on July 6 2011 --- Implementation Version --- core tasks : 1.8.2 in file:/usr/share/java/ant.jar --- ANT PROPERTIES --- ant.version: Apache Ant(TM) version 1.8.2 compiled on July 6 2011 ant.java.version: 1.6 Is this the Apache Harmony VM? no Is this the Kaffe VM? no Is this gij/gcj? no ant.core.lib: /usr/share/java/ant.jar ant.home: /usr/share/ant --- ANT_HOME/lib jar listing --- ant.home: /usr/share/ant ant-junit.jar (102000 bytes) ant.jar (1935105 bytes) ant-bootstrap.jar (19759 bytes) ant-launcher.jar (12307 bytes) --- USER_HOME/.ant/lib jar listing --- user.home: /opt/devel maven-ant-tasks.jar (61063 bytes) --- Tasks availability --- p4reopen : Not Available (the implementation class is not present) ...(cut short for simplicity) ddcreator : Not Available (the implementation class is not present) A task being missing/unavailable should only matter if you are trying to use it --- org.apache.env.Which diagnostics --- Not available. Download it at http://xml.apache.org/commons/ --- XML Parser information --- XML Parser : org.apache.xerces.jaxp.SAXParserImpl XML Parser Location: file:/usr/share/java/xerces-j2-2.11.0.jar Namespace-aware parser : org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser Namespace-aware parser Location: file:/usr/share/java/xerces-j2-2.11.0.jar --- XSLT Processor information --- XSLT Processor : com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl XSLT Processor Location: unknown --- System properties --- java.runtime.name : OpenJDK Runtime Environment sun.boot.library.path : /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64 java.vm.version : 20.0-b11 ant.library.dir : /usr/share/ant/lib java.vm.vendor : Sun Microsystems Inc. java.vendor.url : http://java.sun.com/ path.separator : : java.vm.name : OpenJDK 64-Bit Server VM file.encoding.pkg : sun.io user.country : US sun.java.launcher : SUN_STANDARD sun.os.patch.level : unknown java.vm.specification.name : Java Virtual Machine Specification user.dir : /opt/devel/test java.runtime.version : 1.6.0_22-b22 java.awt.graphicsenv : sun.awt.X11GraphicsEnvironment java.endorsed.dirs : /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/endorsed os.arch : amd64 java.io.tmpdir : /tmp line.separator : java.vm.specification.vendor : Sun Microsystems Inc. os.name : Linux ant.home : /usr/share/ant
Re: Best way to handle an ssh copy?
Although it is not fully reliable, what works for me is to use the maven-exec-plugin to directly invoke ssh/scp command. The issue is mainly that you cannot be sure that ssh or scp is installed on the computer maven is running on. But, in all likelyhood: * Linux: usually ssh/scp is installed (although it could be removed, I don't see that that often, not to say that I have never seen this) * Mac: ssh/scp is always installed (to my knowledge at least) * Windows: I always have cygwin installed and cygwin's bin directory is in the PATH env variable Making these assumptions, I find that this is quite reliable and really straightforward to use. Cheers, Guillaume Le 15/12/2011 18:08, Tom Masterson a écrit : So if I don't use the wagon plugin do you have a sugestion as to what I should use? I am not finding anything else out there when I do a google search. Tom On Thu, 15 Dec 2011, Benson Margulies wrote: On Wed, Dec 14, 2011 at 6:26 PM, Tom Masterson kd7...@gmail.com wrote: We have several artifacts that we want to copy to remote servers via scp/ssh. I have looked at the wagon plugin but the documentation seems to have issues. DO NOT try to use the Wagon plugin. It is *not* a tool for arbitrary SCPs. It is only defined to work with Maven repos. You can sometimes accidently get it to do what you want for something else, but that's it. When I try to use it as documented I get an error telling me it can't find a plugin descriptor for wagon-ssh. Is there a good way to get maven to scp files to a remote server and where can I find documentation on how to do this. Thank TOm - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin configuration and property precedence question
use mvn help:effective-pom to find out. My guess would be 1.5. Cheers, Guillaume Le 13/12/2011 18:31, Laird Nelson a écrit : I've noticed that some plugins feature expressions that, when present as properties, will override configuration values. So, taking the maven-compiler-plugin as an arbitrary example, I can configure its source property like this: configuration source1.6/source /configuration ...or I could simply set a property in my pom.xml file (i.e. instead of the configuration above): maven.compiler.source1.6/maven.compiler.source !-- the expression is defined according to the docs as maven.compiler.source -- ...or I could eliminate that and make sure that I always specified the following on the command line (an admittedly contrived solution): -Dmaven.compiler.source=1.6 So far this all makes sense to me. Now let's introduce inheritance. Suppose I have a pom.xml that extends another one. Suppose the parent opts for solution #2 above. That is, inside itsproperties section it does this: maven.compiler.source*1.6*/maven.compiler.source ...and furthermore does not specify an explicit configuration for the maven-compiler-plugin. Now suppose the child introduces this: configuration source*1.5*/source /configuration Will the maven-compiler-plugin executed in the child be configured with (at build time) a source value of 1.6 or 1.5? Thanks, Laird - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Any idea on choosing Repository - Archiva vs Artifactory
Keep in mind that this article is mainly written directly by the guys developing those software and two of them have a commercial version, meaning that they are pretty focused on making their tool bright and shiny. Cheers, Guillaume Le 13/12/2011 00:17, Daivish Shah a écrit : Thanks Pawan !! this helps a lot !! On Mon, Dec 12, 2011 at 2:31 PM, Gandhi, Pawan gandhi.pa...@pennmutual.comwrote: Below link may help you http://docs.codehaus.org/display/MAVENUSER/Maven+Repository+Manager+Feature+Matrix Thanks Pawan -Original Message- From: Daivish Shah [mailto:daivish.s...@gmail.com] Sent: Monday, December 12, 2011 5:23 PM To: Maven Users List Subject: Any idea on choosing Repository - Archiva vs Artifactory Hi, I am trying to find comparison on Archiva vs Artificatory but i couldn't find any good discussion URL on these specific 2 repositories. Can anybody tell me which one is good repository to USE ? and what's the reason behind that ? Please help me out on this one. Thanks, daivish. This message, including any attachments, is intended only for the recipient(s) named above. It may contain confidential and privileged information. If you have received this communication in error, please notify the sender immediately and destroy or delete the original message. Also, please be aware that if you are not the intended recipient, any review, disclosure, copying, distribution or any action or reliance based on this message is prohibited by law. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maintaining same version
I think that what he was trying to achieve is to not repeat the same version in all the pom's but this is totally impossible because of the way Maven works. Guillaume Le 11/12/2011 18:24, Benson Margulies a écrit : You do this by inheriting the version through the parent element. You have to repeat the version once in each pom: as the plain version in the top pom, and then in the parent element of the others. Controlling the version through a parameter is not a good idea. The versions plugin can help you with this, as will the release plugin. On Sun, Dec 11, 2011 at 11:16 AM, Prashant Neginahal prashu.n...@gmail.com wrote: HI All, We have project structure like below for an app, app-project-a app-multi-module-bc --app-project-b --app-project-c app-project-d We would like to have same version for all projects in app. I was thinking about having a property APP_VERSION in all parent POM and use thisversion in all projects. But, how does this maven release plug-in works in this approach? Many Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maintaining same version
Sure, writing it in the parent definition is the best way to go since you avoid to write it twice. This is the way I work at least. Sorry if I made that unclear with my previous e-mail. Guillaume Le 13/12/2011 01:07, Barrie Treloar a écrit : On Tue, Dec 13, 2011 at 9:24 AM, Guillaume Polet guillaume.po...@gmail.com wrote: I think that what he was trying to achieve is to not repeat the same version in all the pom's but this is totally impossible because of the way Maven works. Yes, but at least you only need to define it once for each module (in the parent/version section). Only the parent pom needs to define the versions in the dependencyManagement section. And as Benson points out, doing it this way release (or vesrions plugin) will manage it for you. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Parallel development on multiple dependent projects
I think you are looking for the SNAPSHOT of your projects. You just have to add -SNAPSHOT behind your version (in both the your depending on project and your dependency) version1.0-SNAPSHOT/version Cheers, Guillaume Le 29/11/2011 15:42, Abid Hussain a écrit : Hi all, I wonder if maven can handle the scenario when multiple projects (which are dependent on each other) are developed concurrently. E.g. we have a project A which is dependent on projects B and C. All projects are at development stage. When developing on A one wants to use the latest features in dependent projects B and C at current development stage. As one has to declare a certain version number in A's pom.xml there is no way to tell maven always to use the development-version (or trunk-version) of B and C which haven't been released so far. So, is there a way to declare dependencies on modules which haven't been released so far? Regards, Abid - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Uncompiled classes resulting in COMPILATION ERROR : cannot find symbol
Well, I think I finally found the root issue of this and I was quite astonished by what I have discovered. Anyway, the first thing I did was fixing 8 Warnings I had about using Sun proprietary code--OK this was not nice from me, but it had worked for so many years that I was wondering if there was any point to these warnings. And ok, warnings are not good but they should not ruin everything either. Once I did that, the root cause finally unrevealed itself: [ERROR] Failure executing javac, but could not parse the error: [ERROR] An exception has occurred in the compiler (1.6.0_26). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following d iagnostic in your report. Thank you. [ERROR] java.lang.NullPointerException [ERROR] at com.sun.tools.javac.comp.Check.checkCompatibleConcretes(Check.java:12 15) [ERROR] at com.sun.tools.javac.comp.Check.checkCompatibleSupertypes(Check.java:1 567) [ERROR] at com.sun.tools.javac.comp.Attr.attribClassBody(Attr.java:2674) [ERROR] at com.sun.tools.javac.comp.Attr.attribClass(Attr.java:2628) [ERROR] at com.sun.tools.javac.comp.Attr.attribClass(Attr.java:2564) [ERROR] at com.sun.tools.javac.main.JavaCompiler.attribute(JavaCompiler.java:103 6) [ERROR] at com.sun.tools.javac.main.JavaCompiler.compile2(JavaCompiler.java:765) [ERROR] at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:730) [ERROR] at com.sun.tools.javac.main.Main.compile(Main.java:353) [ERROR] at com.sun.tools.javac.main.Main.compile(Main.java:279) [ERROR] at com.sun.tools.javac.main.Main.compile(Main.java:270) [ERROR] at com.sun.tools.javac.Main.compile(Main.java:69) [ERROR] at com.sun.tools.javac.Main.main(Main.java:54) [ERROR] - [Help 1] [ERROR] So, just by removing some warnings, the Java compiler finally decided itself to report to me that it was unable to compile some classes. After looking around, I found that this issue is 6 years old, many guys have had this NPE, and it should be fixed in JVM 7. Hopefully, this may help some other people having this error, but I got to say that I never had such severe issues with Sun/Oracle JVM until now. Makes me wonder if I should keep on compiling with this JVM. Cheers, Guillaume Le 20/10/2011 09:15, bgik a écrit : Hi Maybe i should add some clarification. We don't use Jenkins, so my issue was related purely to the fact classes under src/main in my module failed to compile using mvn release:perform, meaning classes under src/test then failed with missing symbols. Increasing the heap size worked for the 3 of us on my team previously seeing the issue. Agree that it would be nice to raise a bug, but in the absence of any test case to show the issue i haven't done. Sorry it doesn't help you much thanks -- View this message in context: http://maven.40175.n5.nabble.com/Uncompiled-classes-resulting-in-COMPILATION-ERROR-cannot-find-symbol-tp4903264p4920568.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Uncompiled classes resulting in COMPILATION ERROR : cannot find symbol
OK, thanks for your answers. On my side, I made sure that those issues arise on both my laptop and on jenkins. I have also tried your suggestions on both, but unfortunately they did not work for me. Anyway, thanks again for spending the time to reply. Cheers, Guillaume Le 20/10/2011 09:15, bgik a écrit : Hi Maybe i should add some clarification. We don't use Jenkins, so my issue was related purely to the fact classes under src/main in my module failed to compile using mvn release:perform, meaning classes under src/test then failed with missing symbols. Increasing the heap size worked for the 3 of us on my team previously seeing the issue. Agree that it would be nice to raise a bug, but in the absence of any test case to show the issue i haven't done. Sorry it doesn't help you much thanks -- View this message in context: http://maven.40175.n5.nabble.com/Uncompiled-classes-resulting-in-COMPILATION-ERROR-cannot-find-symbol-tp4903264p4920568.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: zip instead of jar
Hi, from my point of view, I would rather use the Maven assembly plugin since: * the documentation if far more complete * it may meet additional future requirements * it seems more active Its usage is all explained on their website: http://maven.apache.org/plugins/maven-assembly-plugin/usage.html You could probably go with the build-in descriptor reference 'bin' but it produces two additional artifacts (tar.gz and tar.bz2). If you feel lost with the usage of plugins, I can only advice you to read the Maven user documentation: * http://maven.apache.org/guides/getting-started/index.html, and more specifically * http://maven.apache.org/guides/getting-started/index.html#How_do_I_use_plug-ins Cheers, Guillaume Le 19/10/2011 10:08, louis_xie a écrit : Hi, I know this post has been quite dated to date, however, i believe it continues to be relevant to many out there trying to create a zip package. I have found a maven zip plugin at http://people.apache.org/~olamy/snapshots/maven-zip-plugin/index.html http://people.apache.org/~olamy/snapshots/maven-zip-plugin/index.html . However, I do not know how I could download this to include in my project. Please pardon me as I'm a complete noob to Maven, and have no experience in build scripts either. Would appreciate your patience. Thanks! -- View this message in context: http://maven.40175.n5.nabble.com/zip-instead-of-jar-tp111889p4916811.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Uncompiled classes resulting in COMPILATION ERROR : cannot find symbol
Thank you very much for the kind response. I just made several attempts according to your remarks: 1) Increasing the Heap size to 1G (it used to be 512M)-- that did not work 2) I then tried to configure the maven compiler plugin to fork-- that did not work either 3) I also increases the maxmem of the m-c-p to 1G and with fork activated--still no luck :'( Could it be that you also changed something else? Anyway, I find it very disturbing that with 2 projects in jenkins with the exact same configuration to the exception of their name (the one that works has a suffix '_2'), one of them works and not the other. Moreover, if the java compiler encounters an OOME, it should definitely fail the build instead of silently continue. I think that if you can find an example that can pin-point this kind of issue, you should report it as a bug. Although, I think I have already encountered OOME in the past and I think it failed the build. Cheers, Guillaume Le 19/10/2011 15:53, bgik a écrit : I saw the same issue this week. It appeared after a colleague merged in a large piece of work from a branch. The remedy for us was to increase the heap size used by maven by setting MAVEN_OPTS. So i suspect it's caused by some 'silent' OutOfMemory error. If you havent tried this, trying increasing the heap size. thanks -- View this message in context: http://maven.40175.n5.nabble.com/Uncompiled-classes-resulting-in-COMPILATION-ERROR-cannot-find-symbol-tp4903264p4917796.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Uncompiled classes resulting in COMPILATION ERROR : cannot find symbol
Well this would have been my guess too, but as I mentionned earlier in another e-mail, I can also reproduce this on my laptop where there is absolutely no trace of jenkins. If you have git and maven on your path, you can reproduce this issue with this: * Checkout the code: git clone git://github.com/agilebirds/openflexo.git * Go into the checked-out code: cd openflexo * Build the project: mvn -DskipTests clean package (I know, skipping test is a bad practice, but one step at a time...) But maybe you will not have this issue (it comes up when compiling the test-classes of FlexoFoundation) and so this will definitely point into the direction of an environment issue. Cheers, Guillaume Le 19/10/2011 18:09, Wayne Fay a écrit : Could it be that you also changed something else? Anyway, I find it very disturbing that with 2 projects in jenkins with the exact same configuration to the exception of their name (the one that works has a suffix '_2'), one of them works and not the other. Does this not point to perhaps an issue in Jenkins then? I don't see how this is possible either. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Uncompiled classes resulting in COMPILATION ERROR : cannot find symbol
Ok more info on this issue which is driving me nuts. I reset everything this week-end and I still get the error: https://test.openflexo.com/jenkins/job/openflexo/8/console Now, weirdest thing is that I have another build which is the nightly build of the same project and the build succeeds: https://test.openflexo.com/jenkins/job/openflexo_nightly/81/console Finally, I created a copy of the openflexo build in openflexo_2 and it also worked (the only difference there is the job name). So my conclusion was that jenkins has some kind of really screwed up cache somewhere which screws my project openflexo. But before going to jenkins ML, I tried one last thing on my laptop: * Checkout the code: git clone git://github.com/agilebirds/openflexo.git * Go into the checked-out code: cd openflexo * Build the project: mvn -DskipTests clean package (I know, skipping test is a bad practice, but one step at a time...) Bang I hit the same error again, so I am back to square 1. My laptop has the following configuration: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: D:\Work\apache-maven-3.0.3\bin\.. Java version: 1.6.0_26, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_26\jre Default locale: fr_BE, platform encoding: Cp1252 OS name: windows 7, version: 6.1, arch: amd64, family: windows And the server running jenkins: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: /home/jenkins/tools/Maven3 Java version: 1.6.0_07, vendor: Sun Microsystems Inc. Java home: /opt/sun-jdk-1.6.0.07/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: linux, version: 2.6.25-gentoo-r7, arch: i386, family: unix Any suggestion is more than welcome although I have some kind of workaround with this renamed job, but I find it ugly to maintain. Cheers, Guillaume Le 14/10/2011 21:28, Kiren Pillay a écrit : Hi Guillaume, Shot in the dark, maybe the build server disk is full? On Fri, Oct 14, 2011 at 7:05 PM, Guillaume Polet guillaume.po...@gmail.com wrote: Hi list, ok this sounds like the simplest question but either my brain fried this evening and I can't see the obvious or else I hit some really unexpected behaviour. I have a multi-module project hosted on github (https://github.com/agilebirds/openflexo) and it is built regularly on jenkins. Somehow, jenkins got messed up and I don't know exactly when my build broke, but it has worked for at least 2 months every night. Anyway, the error I get is the following (classical error): [INFO] [INFO] Building FlexoFoundation 1.4.4-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ flexofoundation --- [INFO] Deleting D:\tmp\openflexo\flexodesktop\model\flexofoundation\target [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ flexofou ndation --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 0 resource [INFO] Copying 0 resource [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ flexofoundati on --- [INFO] Compiling 1542 source files to D:\tmp\openflexo\flexodesktop\model\flexof oundation\target\classes [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\rm\FlexoProject.java:[180,31] com.sun.image.codec.jpeg.JPEGCo dec is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\rm\FlexoProject.java:[181,31] com.sun.image.codec.jpeg.JPEGIm ageEncoder is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\gen\ScreenshotGenerator.java:[59,31] com.sun.image.codec.jpeg .ImageFormatException is Sun proprietary API and may be removed in a future rele ase [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\gen\ScreenshotGenerator.java:[60,31] com.sun.image.codec.jpeg .JPEGCodec is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\rm\FlexoProject.java:[3018,5] com.sun.image.codec.jpeg.JPEGIm ageEncoder is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\rm\FlexoProject.java:[3018,32] com.sun.image.codec.jpeg.JPEGC odec is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\gen\ScreenshotGenerator.java:[418,35] com.sun.image.codec.jpe g.JPEGCodec is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo
Uncompiled classes resulting in COMPILATION ERROR : cannot find symbol
Hi list, ok this sounds like the simplest question but either my brain fried this evening and I can't see the obvious or else I hit some really unexpected behaviour. I have a multi-module project hosted on github (https://github.com/agilebirds/openflexo) and it is built regularly on jenkins. Somehow, jenkins got messed up and I don't know exactly when my build broke, but it has worked for at least 2 months every night. Anyway, the error I get is the following (classical error): [INFO] [INFO] Building FlexoFoundation 1.4.4-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ flexofoundation --- [INFO] Deleting D:\tmp\openflexo\flexodesktop\model\flexofoundation\target [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ flexofou ndation --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 0 resource [INFO] Copying 0 resource [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ flexofoundati on --- [INFO] Compiling 1542 source files to D:\tmp\openflexo\flexodesktop\model\flexof oundation\target\classes [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\rm\FlexoProject.java:[180,31] com.sun.image.codec.jpeg.JPEGCo dec is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\rm\FlexoProject.java:[181,31] com.sun.image.codec.jpeg.JPEGIm ageEncoder is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\gen\ScreenshotGenerator.java:[59,31] com.sun.image.codec.jpeg .ImageFormatException is Sun proprietary API and may be removed in a future rele ase [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\gen\ScreenshotGenerator.java:[60,31] com.sun.image.codec.jpeg .JPEGCodec is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\rm\FlexoProject.java:[3018,5] com.sun.image.codec.jpeg.JPEGIm ageEncoder is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\rm\FlexoProject.java:[3018,32] com.sun.image.codec.jpeg.JPEGC odec is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\gen\ScreenshotGenerator.java:[418,35] com.sun.image.codec.jpe g.JPEGCodec is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\gen\ScreenshotGenerator.java:[426,21] com.sun.image.codec.jpe g.ImageFormatException is Sun proprietary API and may be removed in a future rel ease [INFO] [INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ flexofoundation --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 41 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ flexo foundation --- [INFO] Compiling 27 source files to D:\tmp\openflexo\flexodesktop\model\flexofou ndation\target\test-classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] \tmp\openflexo\flexodesktop\model\flexofoundation\src\test\java\org\open flexo\foundation\FlexoTestCase.java:[40,34] cannot find symbol symbol : class ComponentDMEntity location: package org.openflexo.foundation.dm ... and it goes on and on with the same error but for different classes. Now the thing is that the classes Maven complains it cannot find are in the same project, they just are not test-classes. So I thought that my workspace was all messed up and I went to see on the HD if the corresponding java source files were there or not: all files seems to be present and ok, but when I go to the target directory and look for the corresponding class files, I see that many of them are missing. So I was wondering how would Maven not compile all classes located in src/main/java? I have counted the number of Java files in src/main/java-- 1542 java files and I have counted the number of class files in target/classes: 629 files. How is this possible? I use the following command to perform my goals and options: '-DskipTests clean deploy'. I thought that this could be environmental and so I decided to checkout the code in a clean repository on my laptop, and I also hit the same
Re: Uncompiled classes resulting in COMPILATION ERROR : cannot find symbol
Thanks for the response but unfortunately no, I still have 48G on the server and my laptop has even more. Cheers, Guillaume Le 14/10/2011 21:28, Kiren Pillay a écrit : Hi Guillaume, Shot in the dark, maybe the build server disk is full? On Fri, Oct 14, 2011 at 7:05 PM, Guillaume Polet guillaume.po...@gmail.com wrote: Hi list, ok this sounds like the simplest question but either my brain fried this evening and I can't see the obvious or else I hit some really unexpected behaviour. I have a multi-module project hosted on github (https://github.com/agilebirds/openflexo) and it is built regularly on jenkins. Somehow, jenkins got messed up and I don't know exactly when my build broke, but it has worked for at least 2 months every night. Anyway, the error I get is the following (classical error): [INFO] [INFO] Building FlexoFoundation 1.4.4-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ flexofoundation --- [INFO] Deleting D:\tmp\openflexo\flexodesktop\model\flexofoundation\target [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ flexofou ndation --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 0 resource [INFO] Copying 0 resource [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ flexofoundati on --- [INFO] Compiling 1542 source files to D:\tmp\openflexo\flexodesktop\model\flexof oundation\target\classes [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\rm\FlexoProject.java:[180,31] com.sun.image.codec.jpeg.JPEGCo dec is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\rm\FlexoProject.java:[181,31] com.sun.image.codec.jpeg.JPEGIm ageEncoder is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\gen\ScreenshotGenerator.java:[59,31] com.sun.image.codec.jpeg .ImageFormatException is Sun proprietary API and may be removed in a future rele ase [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\gen\ScreenshotGenerator.java:[60,31] com.sun.image.codec.jpeg .JPEGCodec is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\rm\FlexoProject.java:[3018,5] com.sun.image.codec.jpeg.JPEGIm ageEncoder is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\rm\FlexoProject.java:[3018,32] com.sun.image.codec.jpeg.JPEGC odec is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\gen\ScreenshotGenerator.java:[418,35] com.sun.image.codec.jpe g.JPEGCodec is Sun proprietary API and may be removed in a future release [WARNING] \tmp\openflexo\flexodesktop\model\flexofoundation\src\main\java\org\op enflexo\foundation\gen\ScreenshotGenerator.java:[426,21] com.sun.image.codec.jpe g.ImageFormatException is Sun proprietary API and may be removed in a future rel ease [INFO] [INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ flexofoundation --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 41 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ flexo foundation --- [INFO] Compiling 27 source files to D:\tmp\openflexo\flexodesktop\model\flexofou ndation\target\test-classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] \tmp\openflexo\flexodesktop\model\flexofoundation\src\test\java\org\open flexo\foundation\FlexoTestCase.java:[40,34] cannot find symbol symbol : class ComponentDMEntity location: package org.openflexo.foundation.dm ... and it goes on and on with the same error but for different classes. Now the thing is that the classes Maven complains it cannot find are in the same project, they just are not test-classes. So I thought that my workspace was all messed up and I went to see on the HD if the corresponding java source files were there or not: all files seems to be present and ok, but when I go to the target directory and look for the corresponding class files, I see that many of them are missing. So I was wondering how would Maven not compile all classes located in src/main/java? I have counted the number of Java files in src/main/java-- 1542 java files and I have counted the number of class files in target/classes: 629
Re: default auth for settings.xml
I think that what he meant was that: 1) Having the same password on different servers is a poor security practice 2) If you have different passwords, then you will not try to set them once for all since they will be different. Not sure all these apply to your case. As far as I understand your question, it seems quite reasonable to me. Cheers, Guillaume Le 13/10/2011 20:57, Tommy Chheng a écrit : To clarify, it's the same account on the same nexus repo. The server ids are different because each is a different proxied server. How would the original problem vanish by changing the password for each server entry? On Thu, Oct 13, 2011 at 11:48 AM, Ansgar Konermann ansgar.konerm...@googlemail.com wrote: Am 13.10.2011 20:06, schrieb Tommy Chheng: I have a few servers in the settings.xml where the username/password is the same for all server ids. Hi, use a different password for different servers. The server administrators will probably be very grateful for this fine act of computer security. Besides, your original problem will vanish. Best regards Ansgar - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Parent Dependencies
Hi,
So I have briefly read your pom.xml and it seems that you have put the
dependency for spring in the dependencyMgmt element and not in the
dependencies element. So let me straight things out here:
* dependencyMgmt are used to declare version number, configuration,
scope, etc... but it does not mean that you depend on them, you just
inform Maven of the default values to use, if they are not defined in
the dependencies element.
* dependencies are used to declare on which artifacts your project(s)
depend. If you do not define version, scope, etc..., Maven will try to
pick them up from the dependencyMgmt.
A best practice is to define in your super pom, the version of all your
dependencies of all your project in the dependencyMgmt and then simply
instantiate those dependency in each child project. This allows you to
centralize all the versions of all jars used in all projects.
So in your super pom you define:
dependencyMgmt
dependency
groupIdx.y.z/groupId
artifactIdazerty/artifactId
version1.2.3/version
/dependency
...
/dependencyMgmt
Then in your child pom you can simply put:
dependencies
dependency
groupIdx.y.z/groupId
artifactIdazerty/artifactId
/dependency
...
/dependencies
without the version number, and Maven will automatically find that you
want version 1.2.3. Yet, you can still override this default value by
setting the version number in the child pom.
In the dependency
Le 30/09/2011 11:02, Kiren Pillay a écrit :
Hi
I think our project is misconfigured. From reading the docs again, the
common dependencies go to within the dependencyManagent tag (we where
using the dependencies before).
I've fixed this but still see that the dependencies declared in the
super pom aren't being picked up by the children.
For instance the springframeork annotation package isn't being picked
up even though its in the super pom.
[ERROR]
/home/kiren/Documents/workspace-subsnp/pams-main/core/advantage/src/main/java/za/co/vodacom/pams/core/in/dao/INSubscriberProfileDaoImpl.java:[4,51]
package org.springframework.beans.factory.annotation does not exist
Child:
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
parent
groupIdza.co.vodacom.pams/groupId
artifactIdpams-core/artifactId
version1.2.1-DEV-SNAPSHOT/version
/parent
groupIdza.co.vodacom.pams/groupId
artifactIdpams-advantage/artifactId
version1.2.1-DEV-SNAPSHOT/version
namePAMS Core - IN DAO/name
packagingjar/packaging
dependencies
!-- IN Advantage CORBA Interface --
dependency
groupIdza.co.vodacom.advantage/groupId
artifactIdadvantage-corba-interface/artifactId
/dependency
dependency
groupIdza.co.vodacom.fap/groupId
artifactIdfap-core/artifactId
version${fcaps.version}/version
typejar/type
scopecompile/scope
/dependency
/dependencies
build
plugins
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
source${java.source.version}/source
target${java.target.version}/target
showDeprecationtrue/showDeprecation
/configuration
/plugin
plugin
artifactIdmaven-surefire-plugin/artifactId
configuration
forkModenever/forkMode
/configuration
/plugin
/plugins
/build
/project
Parent:
?xml version=1.0 encoding=UTF-8?
projectxmlns=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/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
parent
groupIdza.co.vodacom.pams/groupId
artifactIdpams-main/artifactId
version1.2.1-DEV-SNAPSHOT/version
/parent
groupIdza.co.vodacom.pams/groupId
artifactIdpams-core/artifactId
namePAMS Core/name
packagingpom/packaging
version1.2.1-DEV-SNAPSHOT/version
modules
!-- common used project need to be before other, chicken and egg--
modulecommon/module
modulepams-schema/module
moduleadvantage/module
moduleppfe-connectors/module
moduleppfe_dao/module
modulepams-rms-dao/module
modulepams-pams-dao/module
!--moduleaudit/module --
modulepams-cur-dao/module
/modules
/project
Super (Grandparent)
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
Re: Using Maven with custom libraries which are not in repository.
I am looking at fix to use that framework in maven way. Then, your only option is to install all those jars in your Nexus repository. Guillaume Le 29/09/2011 09:31, Prashant Neginahal a écrit : Thanks for reply,Yuvaraj. I understand the maven repository and we will be having nexus repository. But, we are asked to use that proprietary web framework which comes with its own jars. I dont think we have possibility to mavenize all those jars and put them into repository. I just want to keep it the way it is and use for build. However, our application development projects will be maven projects and will put them into maven repository. Thanks, Prashant On Thu, Sep 29, 2011 at 12:17 PM, Yuvaraj Vanarase yuvaraj.vanar...@synechron.com wrote: Prashant, If those libraries are standard and well known then should be available at some maven repository. You can try http://mvnrepository.com to find it out. Generally, you should setup your own repository may be using artifactory and put all dependencies there. Requirement is maven should able to access those jars while build, once artifact is ready it will contain required jars, thus complete deployable. Hope this helps! Regards, Yuvaraj Yuvaraj Vanarase, Lead Technology - Software Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 | http://www.synechron.com SYNECHRON - - Top 10 Best IT Employers for 4 consecutive years (link). - Celebrating 10 Years! -Original Message- From: Prashant Neginahal [mailto:prashu.n...@gmail.com] Sent: Thursday, September 29, 2011 12:14 PM To: Maven Users List Subject: Using Maven with custom libraries which are not in repository. Hi All, We are starting new web project. But, it has to be built on some proprietary web framework which is NOT mavenised and comes with its own bunch of libraries. I am thinking of using maven for this application development. But, just wondering how to ensure maven uses this proprietary framework and its libraries which are not there in repository. Can we just dump framework libraries in WEB_INF/lib folder and maven includes the same in its CLASSPATH. Thanks, Prashant - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Parent Dependencies
I am not sure I understood you correctly but here is what I can tell: Let's say you have a Main project which contains two modules: dao and business: * Main o dao o business If in your Main pom.xml, you have defined the following: groupIda.b.c/groupId artifactIdMain/artifactId version1.0version dependencies dependency groupIdx.y.z/groupId artifactIdazerty/artifactId version1.0/version /dependency dependencies If in your dao pom.xml, you have defined the following parent groupIda.b.c/groupId artifactIdMain/artifactId version1.0version /parent then yes, you should inherit the dependency provided in you Main pom.xml, ie, in my example: groupIdx.y.z/groupId artifactIdazerty/artifactId version1.0/version Without any more information, it will be hard to help more I think. Cheers, Guillaume Le 29/09/2011 11:32, Kiren Pillay a écrit : Hi All We have a project with multi-level modules. Main core--dao +---business From what I've read, if I've defined the dependency in the Main module, I don't need to repeat the defintion the dao module. Is this correct, because it doesn't seem to work for me? Regards Kiren - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skip Pom deployment
You must then configure the following property in the maven-deploy-plugin: http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#skip If you want to be able to choose that from the CLI, add a property (let's say skipDeploy) in your parent pom.xml with the value 'true', bind that property to the m-d-p in the parent pom and then you can choose to skip deployment for the parent pom with 'mvn -DskipDeploy=true deploy' which will result in the build and deployment of all the modules except the parent pom. Cheers, Guillaume Le 29/09/2011 12:42, Nazia Ghawte a écrit : How to skip the deployment of parent Pom into the maven repository? -- View this message in context: http://maven-users.828.n2.nabble.com/Skip-Pom-deployment-tp6843439p6843439.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skip Pom deployment
Small errata, by default you should of course set the skipDeploy to 'false' of course so that by default your pom is deployed. G. Le 29/09/2011 13:01, Guillaume Polet a écrit : You must then configure the following property in the maven-deploy-plugin: http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#skip If you want to be able to choose that from the CLI, add a property (let's say skipDeploy) in your parent pom.xml with the value 'true', bind that property to the m-d-p in the parent pom and then you can choose to skip deployment for the parent pom with 'mvn -DskipDeploy=true deploy' which will result in the build and deployment of all the modules except the parent pom. Cheers, Guillaume Le 29/09/2011 12:42, Nazia Ghawte a écrit : How to skip the deployment of parent Pom into the maven repository? -- View this message in context: http://maven-users.828.n2.nabble.com/Skip-Pom-deployment-tp6843439p6843439.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skip Pom deployment
I just tested with the following pom and it works like a charm:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
groupIdx.y.z/groupId
artifactIdtest/artifactId
version1.0-SNAPSHOT/version
nameTest/name
packagingpom/packaging
properties
skipDeployfalse/skipDeploy
/properties
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.7/version
configuration
skip${skipDeploy}/skip
/configuration
/plugin
/plugins
/build
/project
However, there is a major flaw in this solution, because you will have
to redeclare the deploy plugin in all your children to indicate that you
want them to be deployed
I feel like this is getting complicated just to avoid the deployment of
a single pom file. Any good reason for not deploying this pom? Maybe
some Maven-guru has a better option?
Cheers,
Guillaume
Le 29/09/2011 13:11, Nazia Ghawte a écrit :
Thanks for your reply.
i have tried putting the following into the parent POM
properties
skipDeploytrue/skipDeploy
/properties
but it still doesnt work and the pom gets deployed.
--
View this message in context:
http://maven-users.828.n2.nabble.com/Skip-Pom-deployment-tp6843439p6843521.html
Sent from the maven users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Parent Dependencies
Sure, the inheritance is transitive. You can have as many levels as you want: If you have a hierarchy like this: * A o B + C All dependencies declared in A will also be available for B and C and all dependencies declared in B will also be available for C. Guillaume Le 29/09/2011 12:57, Kiren Pillay a écrit : Thanks for the explanation Guillame...this works as you've stated. However my question is, is the inheritance transitive, i.e, the child pom would inherit the dependencies of the grandparent pom? From what I'm seeing this is not the case. Regards On Thu, Sep 29, 2011 at 11:43 AM, Guillaume Polet guillaume.po...@gmail.com wrote: I am not sure I understood you correctly but here is what I can tell: Let's say you have a Main project which contains two modules: dao and business: * Main o dao o business If in your Main pom.xml, you have defined the following: groupIda.b.c/groupId artifactIdMain/artifactId version1.0version dependencies dependency groupIdx.y.z/groupId artifactIdazerty/artifactId version1.0/version /dependency dependencies If in your dao pom.xml, you have defined the following parent groupIda.b.c/groupId artifactIdMain/artifactId version1.0version /parent then yes, you should inherit the dependency provided in you Main pom.xml, ie, in my example: groupIdx.y.z/groupId artifactIdazerty/artifactId version1.0/version Without any more information, it will be hard to help more I think. Cheers, Guillaume Le 29/09/2011 11:32, Kiren Pillay a écrit : Hi All We have a project with multi-level modules. Main core--dao +---business From what I've read, if I've defined the dependency in the Main module, I don't need to repeat the defintion the dao module. Is this correct, because it doesn't seem to work for me? Regards Kiren - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skip Pom deployment
Ok, I guess I am missing something here, but if you run 'mvn deploy' from one of your child module, then only that module (and its child modules, if any) is build and deployed. The parent pom is deployed only if you run 'mvn deploy' from the parent or one of its ancestor. Can you post your pom's here ? Cheers, Guillaume Le 29/09/2011 14:21, Nazia Ghawte a écrit : i have tried again but with no success. the main reason for the POM not to be deployed because it is only needed when i run the parent project,where as the child modules are independant of each other and can be built on their own as well.the parent module is only needed to be built if we want all the artifacts in the project to be freshly built all at once. Any solutions? -- View this message in context: http://maven-users.828.n2.nabble.com/Skip-Pom-deployment-tp6843439p6843668.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skip Pom deployment
You mean that if you run twice the exact same command, you get two
different results? Then there is something really wrong with your project.
Anyway, let's say you have a project with the following structure:
* Root
o A
o B
o C
in Root, you declare the 3 modules A,B,C (aggregation), and in A,B,C,
you declare Root as their parent (inheritance).
If you run 'mvn deploy' from Root, all four projects should get
deployed. If you run 'mvn deploy' from A, B or C, then only A, B or C
should get deployed. Isn't this what you are looking for?
Guillaume
Le 29/09/2011 14:30, Nazia Ghawte a écrit :
ok, one revelation here.
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.7/version
configuration
skip${skipDeploy}/skip
/configuration
/plugin
On changing the plugin version from 2.4 to 2.7 the artifact deployment was
skipped for the first time,but it agin got deployed on running the deploy
command for the second time.
--
View this message in context:
http://maven-users.828.n2.nabble.com/Skip-Pom-deployment-tp6843439p6843702.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: Skip Pom deployment
Sorry but you got me lost there. I really don't know how you get very two different results running the same command with the same parameters and without changing the pom.xml's. Do you run those with a command line or do you use an IDE? Maybe somebody else has a better understanding than I am of what your problem is. Anyway, I don't see why you would have to modify anything to your pom, since the result you want can be obtained just by changing the current directory when launching Maven. Hope someone can help you more. Guillaume Le 29/09/2011 14:53, Nazia Ghawte a écrit : Follwoing is the output on running the deploy command First when i chnage the version from 2.4 to 2.6 [INFO] Uploading repository metadata for: 'artifact commons.adapter:pricing-ra' [INFO] [INFO] Building Resource Adapter [INFO]task-segment: [deploy] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/2.6/maven-deploy-plugin-2.6.pom Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugins/19/maven-plugins-19.pom Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/2.6/maven-deploy-plugin-2.6.jar [INFO] Reloading plugin container for: org.apache.maven.plugins:maven-deploy-plugin. The plugin artifact has changed. [INFO] [site:attach-descriptor] [INFO] [install:install] [INFO] Installing /home/dev/SVNWorkspace/resourceadapter/pom.xml to /usr/local/apache-maven-2.0.9/repo/com/pf/resourceadapter/1.0-SNAPSHOT/resourceadapter-1.0-SNAPSHOT.pom [INFO] [deploy:deploy] [INFO] Skipping artifact deployment [INFO] [INFO] [INFO] [INFO] Reactor Summary: [INFO] [INFO] commons-adapter ... SUCCESS [9.058s] [INFO] parser SUCCESS [4.884s] [INFO] uri-ra SUCCESS [5.204s] [INFO] tax-ra SUCCESS [5.134s] [INFO] pricing-ra SUCCESS [5.085s] [INFO] Resource Adapter .. SUCCESS [2.941s] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] 2) when i run the same command again [INFO] Uploading repository metadata for: 'artifact commons.adapter:pricing-ra' [INFO] [INFO] Building Resource Adapter [INFO]task-segment: [deploy] [INFO] [INFO] [site:attach-descriptor] [INFO] [install:install] [INFO] Installing /home/dev/SVNWorkspace/resourceadapter/pom.xml to /usr/local/apache-maven-2.0.9/repo/com/pf/resourceadapter/1.0-SNAPSHOT/resourceadapter-1.0-SNAPSHOT.pom [INFO] [deploy:deploy] altDeploymentRepository = null [INFO] Retrieving previous build number from maven Uploading: scp://10.11.19.113/home/dev/com/pf/resourceadapter/1.0-SNAPSHOT/resourceadapter-1.0-20110929.112106-10.pom 4K uploaded [INFO] Retrieving previous metadata from maven [INFO] Uploading repository metadata for: 'artifact com.pf:resourceadapter' [INFO] Retrieving previous metadata from maven [INFO] Uploading repository metadata for: 'snapshot com.pf:resourceadapter:1.0-SNAPSHOT' [INFO] [INFO] [INFO] [INFO] Reactor Summary: [INFO] [INFO] commons-adapter ... SUCCESS [9.585s] [INFO] parser SUCCESS [4.946s] [INFO] uri-ra SUCCESS [5.186s] [INFO] tax-ra SUCCESS [5.059s] [INFO] pricing-ra SUCCESS [5.133s] [INFO] Resource Adapter .. SUCCESS [6.234s] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] -- View this message in context: http://maven-users.828.n2.nabble.com/Skip-Pom-deployment-tp6843439p6843774.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail:
Re: customisation of path in pom
Simply use properties
properties
firefox.path/usr/share/bin/firefox/firefox.path
/properties
and wherever you need that value, just replace by ${firefox.path}
Cheers,
Guillaume
Le 29/09/2011 16:16, sandy a écrit :
Dear friends
I am successful in integrating selenium html tests using maven on my local
machine.
In my pom.xml i give the local path for firefox to run the html test.
how should i do to customise my firefoxpath.
--
View this message in context:
http://maven.40175.n5.nabble.com/customisation-of-path-in-pom-tp4853264p4853264.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Multiple single-module projects vs one multi-module project
You can create a pom project declaring those dependencies and then add a dependency toward that pom project in each project (don't forget to specify typepom/type when declaring that dependency. Cheers, Guillaume Le 28/09/2011 06:52, Behrang Saeedzadeh a écrit : Thanks for affirming this Ron. By the way, how do you ensure that all those projects depend on the same set of external dependences without duplicating the information for each POM? Cheers, Behrang Saeedzadeh http://www.behrang.org On Tue, Sep 27, 2011 at 2:17 AM, Ron Wheeler rwhee...@artifact-software.com wrote: I agree. 4- better visibility into the project for the manager. You know which modules are being changed and which ones are supposed to remain unchanged. You also get a bit of a warning about scope issues or potential problems when a new module gets added to the list of things that need changing after the development plan has been set. 5- more sense of responsibility for testing and the deploying of new SNAPSHOTs and releases. The functional definition of the module tends to be clearer if it is deployed to the team even if it is only a SNAPSHOT. The team expects a personal guaranty to go with a deploy. This tends to make programmers more careful about testing and documenting functionality of stubs and SNAPSHOTs with partial functionality as well as fully functional modules. Ron On 26/09/2011 11:48 AM, Behrang Saeedzadeh wrote: Hi, For large projects, wouldn't multiple single module projects work better than one multi-module project, because: 1- when using a dvcs, the repositories tend to become very large and when the project is divided into multiple single module projects, each project can have a small dvcs repository compared to one large monolithic repo. 2- new developers can be exposed only to the subset of projects that they need to work with 3- finer grained security over which developers can see which parts of the project Thanks in advance, Behrang -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding dependency in pom
Hi,
usually, most dependencies can be found in maven central (you can browse
it here: http://search.maven.org) and by default this is where Maven
looks to resolve dependencies. If your dependencies cannot be found in
central but can be found in another repository (like codehaus, for
example), you have two mechanisms to indicate those repositories to Maven:
1) Add them in your settings.xml (located in ${user.home}/.m2) within an
active profile: http://maven.apache.org/settings.html#Repositories
2) You can add them directly in you pom.xml:
http://maven.apache.org/pom.html#Repositories
There are pros and cons for both options, I am not discussing them now
as this has been already debated several time.
Whatever you choose, you should remove all the jar dependencies from
your Eclipse build path and only keep the Maven Dependencies container.
Cheers,
Guillaume
Le 28/09/2011 13:46, arka.sharma a écrit :
Hi,
I am having a project that I have created in Eclipse.This project conatins
hibernate,drools.So I have added all the necessary jars in the project build
path.Now I have created a maven quickstart archetype where inside main
folder I have kept my java source and inside test directory I have kept my
JUnit test sources.
Now in pom.xml I have added the dependencies by searching dependeny for the
jars I have added in my build path in eclipse.But maven is unable to find
repositories.I can manually install the jars using installer:install but it
is too hectic because there are lots of jars.Is there any easy way to
specify dependency for all the jars used in my project ?
Regards,
Arka
--
View this message in context:
http://maven.40175.n5.nabble.com/Adding-dependency-in-pom-tp4848825p4848825.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [m2] Any support for Cruise Control yet?
Well it seems some people did it here: http://lijinjoseji.wordpress.com/2008/04/29/configuring-cruise-control-with-maven2-and-svn-146-for-continuous-build-environment/ but it was a while ago. Personnally, I use Jenkins which comes with direct support for everything you want, it is easy to install and configure. Cheers, Guillaume Le 26/09/2011 17:37, sreejithsown a écrit : Is it possible to generate html junit, pmd, reports using maven2 and cruise control? Please update if you have any solution. Thanks in advance, Sreejith -- View this message in context: http://maven.40175.n5.nabble.com/m2-Any-support-for-Cruise-Control-yet-tp50718p4841817.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: m-assembly-p problem with dependencies
I think you are mistaking on the semantic of useTransitiveDependency which seems to mean that: * Include/exclude filtering is applied on your direct dependencies, or also on the transtive dependencies (default is to true which seems logical) I believe that what you want is to use an exclude pattern to remove the dependencies of your war project Cheers, Guillaume Le 26/09/2011 19:10, Jesse Farinacci a écrit : Greetings, I am having a lot of problems with the assembly plugin, using Maven 3.0.3 and m-assembly-p 2.2.1. My assembly descriptor and relevant pom.xml information can be found here: https://gist.github.com/1242745 With this configuration, I expect com.acme.proj:bootstrap and its dependencies to be placed directly, unpacked, in the final artifact. For com.acme.proj:war, I expect it to be placed directly, unpacked, in the final artifact BUT not its dependencies. The reason I want this is because my war artifact already contains everything it requires. The bootstrap artifact has lots of other dependencies which are required for proper execution (final assembly is an executable jar), e.g. slf4j, Apache Tomcat, etc. I hope I am just making a stupid mistake, any help on this is greatly appreciated. Thank you! -Jesse - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Setup for Project
From what you expose, I don't see any reason that would prevent you from using Maven. However, you will struggle a little bit to set up sourceDirectory, warDirectory and resourcesDirectory since they are all merged together. You can get around this by setting up correct inclusion/exclusion filters (but I think they will be rather painful to maintain). It would be a lot easier if you can re-organize a bit the files , use maven standard structure (src/main/java, src/main/resources, src/main/webapp ...) and reorganize the projects so that they are not sub-folders of each other. Last time I have set up this kind of project I used the following structure (although there are maybe better solutions, but I found this quite useful): Root parent (you define here anything that should be shared across your project: dependency versions, shared properties, plugin management, etc...) EJB's (to group all your EJB's together) EJB-1 (an EJB project) EJB-2 (another EJB project) ... EAR's (to group all your EAR's together. if you have only one then you can directly put it here instead of having an intermediary node) EAR-1 (an EAR project) EAR-2 (another EAR project) ... JAR's (to group all your standard jars together) JAR-1 JAR-2 ... WAR's (to group all your wars together) WAR-1 WAR-2 ... In this structure, all the nodes are 'pom' project and the leaves of the structure are either 'jar', 'ejb', 'war' or 'ear' projects. As this structure is quite heavy (but provides room for extensibility), you can also use a lighter hierarchy: Root EJB-1 EJB-2 JAR-1 JAR-2 EAR-1 EAR-2 WAR-1 WAR-2 In this structure, only the root node is a 'pom' project, all the others are either 'jar', 'ejb', 'war' or 'ear' projects. In both structure, I would set up the 'pom' project(s) as aggregator (you define the other projects as modules and they reference their upper-level project as their parent). Eventually, you will have to set up the JBoss5 dependencies (with the scope provided). I think that the JBoss repository is now located here: https://repository.jboss.org/nexus/content/groups/public (but it's been a while since I set this up so maybe with a fresher memory will guide you better into which dependencies should be set up). Once you have set up the proper dependencies, you can even remove the "JBoss Container" library from the Eclipse build path. For your Struts dependencies,you can search them here: http://search.maven.org/ and add them where needed. Cheers, Guillaume Le 22/09/2011 07:20, Khavnekar, Pravin a crit: Hello, We are newbies in Maven. We have gone though the Maven Website and develop small Projects on our own as mentioned for the beginners. So far we are very much successful in creating the basic Projects. However, now we want to migrate our current Projects into Maven. Unfortunately, we are facing lot of problems in that. Could you please let us know whether our project structure is feasible to migrate in to Maven? Please find below the structure and technologies used in our Project. Technology: Internet Technology: Servlet, JSP, _javascript_, HTML, CSS and AJAX. Design Tools: MyEclipse 6.0 Server Side Technologies: J2EE - EJB 2.0, Hibernate Frame Work Used: Struts 1.2 Database: PL/SQL Language: Java Web Servers: JBoss 5 Application Server Used: WAS (Deployment Environment), JBoss Application Server. Operating Systems: Win XP (Development), Linux (Production Environment) Project Structure: Please let us know whether it is possible to use Maven and it would
Re: maven build with android API 11 failed, Cann't find symbol
Not much information here, but I guess that when you say 11 you mean that this is the target level. From what it looks like, it seems that android API jars for that version are not available. See also this: http://stackoverflow.com/questions/5253029/why-arent-the-android-sdk-jars-in-any-maven-repository Regarding the message you are mentionning, it just says that the method getActionView cannot be found on the class MenuItem (but the message is quite clear and comes from the java compiler), meaning that Maven is not using the new version you expect. As to why this is the case, without the pom and settings or more information, it is impossible to help you more. Regards, Guillaume Le 19/09/2011 10:35, darakok a écrit : I use maven to build my android project. It was working fine until I make use of method exclusively available to API 11 and above. In the pom file, I do change the android build version to 11. So presume I have set the right android jar for maven build to succeed. But it turns out to be completely the opposite. Because exactly the one method that I just added failed during the build. Maven complains Cannot find symbol: MenuItem.getActionView So do you have any idea what is the problem? Thanks dara kok -- View this message in context: http://maven.40175.n5.nabble.com/maven-build-with-android-API-11-failed-Cann-t-find-symbol-tp4818232p4818232.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven build with android API 11 failed, Cann't find symbol
Find my answers in your e-mail:
Le 19/09/2011 15:20, darakok a écrit :
This is part of my POM file where i specify the version of Android API jar
file to compile with.
plugin
groupIdcom.jayway.maven.plugins.android.generation2/groupId
artifactIdmaven-android-plugin/artifactId
version2.9.0-beta-5/version
configuration
sdk
platform8/platform
/sdk
deleteConflictingFilestrue/deleteConflictingFiles
resourceDirectory${project.build.directory}/filtered-resources
/resourceDirectory
/configuration
extensionstrue/extensions
/plugin
Ok, so If you change here to 11, it does not modify the classpath of the
maven compiler plugin. It simply informs thet maven android plugin that
you are targetting the level 11. The jar used by the maven compiler is
defined in your dependencies.
I'm sure the correct Android jar file is used to compile my project because
it shows the jar file path in the console just before the error comes up.
Interestingly, that same jar file is reference in my project in eclipse and
Eclipse recognize the method that I have problem with when building with
maven.
Can't really know what's going on here since you have not posted your
dependencies and since we don't know where Maven resolves your artifacts
(if you installed the jars manually, you can put whatever version you
want and therefore have an the wrong jar).
Eclipse is of no use here because you can easily add jars through other
means (add a jar, add a library container, etc...). Actually, if you
have such external (to Maven) dependency , you should remove it because
they are not portable from one IDE to another and mainly because this
will not be reflected in your Maven build (probably indicates why you
are having some issues in your build now).
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-build-with-android-API-11-failed-Cann-t-find-symbol-tp4818232p4818946.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
Cheers,
Guillaume
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven build with android API 11 failed, Cann't find symbol
OK, I guess this is the main issue then. From what I understand: * Android guys do not publish their jars to a public Maven repo * If the version used in your dependencies matches the ones used by the Android team, then 2.2= API Level 8. If you want API Level 11, you need version 3.0 (http://developer.android.com/sdk/android-3.0.html) * There are some cool dudes who create jars with Class skeletons and empty method stubs to reproduce all the class names and method signatures so that you can compile your project. Unfortunately, the latests jars have not been created and/or published yet. * There is another guy (who just replied you) who has created a project just for the purpose of deploying the jars from the Android SDK to your local Maven repository: https://github.com/mosabua/maven-android-sdk-deployer. Read this for how to use this tool: https://github.com/mosabua/maven-android-sdk-deployer/blob/master/README.markdown Cheers, Guillaume Le 19/09/2011 16:23, darakok a écrit : I think you're right. My dependency references Android 2.2. dependency groupIdandroid/groupId artifactIdandroid/artifactId version2.2_r2/version scopeprovided/scope /dependency Thanks for your help. darakok -- View this message in context: http://maven.40175.n5.nabble.com/maven-build-with-android-API-11-failed-Cann-t-find-symbol-tp4818232p4819154.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [maven] Re: Auto building parent and sibling projects as needed
Le 11/09/2011 17:37, Jason Pyeron a écrit : -Original Message- From: Guillaume Polet Sent: Sunday, September 11, 2011 4:07 To: Maven Users List Subject: [maven] Re: Auto building parent and sibling projects as needed The problem is that a child does not know where the sources of its parents are located, Is it not the point ofrelativePath../pom.xml/relativePath? No, this simply indicates where to look relatively to find a pom.xml if it is not installed in your local repository (or a remote one where it could be fetched from). and therefore it is completely unable to trigger its build. You probably have set up one or more parent aggregator projects and you mapped this hierarchy onto the file/directory structure but this is not mandatory at all. You can very well use a parent just to define the default version to use for dependencies, or the default target of the compiler, other properties that are common through all your projects and many more things. You should probably read again the first two paragraphs here: http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project _Inheritance_vs_Project_Aggregation Read that before and again. See the bottom of the email and attachment (the poms). The first one explains the benefits of inheritance while the second explain the aggregation. Hope this helps you clear things out. Still stuck at the same place, but thanks for confirming what I read. Cheers, Guillaume Le 11/09/2011 06:21, Jason Pyeron a écrit : I am trying to understand why maven's reactor would not add a parent and a parent's children to the build when it is detected that the dependency is not in the repository. Is there a use case to NOT auto build? Or is there a technical hurdle to overcome to accomplish this in the reactor design? Could I be missing a concept on maven usage? I have a project which has a very large set of parent/child/sibling dependencies I am migrating from our ant build system. When an engineer needs to make changes on their part it would be best for them to execute mvn from that parts directory. Hard to say why your second build is failing. I just tried a similar setup and it worked in all cases: parent: project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdtest/groupId artifactIdparent/artifactId packagingpom/packaging nameparent/name version1.0.0-SNAPSHOT/version modules moduleB/module moduleA/module /modules /project A: project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdtest/groupId artifactIdA/artifactId nameA/name version1.0.0-SNAPSHOT/version packagingpom/packaging parent groupIdtest/groupId artifactIdparent/artifactId version1.0.0-SNAPSHOT/version relativePath../pom.xml/relativePath /parent /project B: project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdtest/groupId artifactIdB/artifactId nameB/name version1.0.0-SNAPSHOT/version packagingpom/packaging parent groupIdtest/groupId artifactIdparent/artifactId version1.0.0-SNAPSHOT/version relativePath../pom.xml/relativePath /parent dependencies dependency groupIdtest/groupId artifactIdA/artifactId version1.0.0-SNAPSHOT/version /dependency /dependencies /project With the directory hierarchy: * parent * A * B and the results from the build: D:\tmp\parentmvn package [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] parent [INFO] A [INFO] B [INFO] [INFO] [INFO] Building parent 1.0.0-SNAPSHOT [INFO] [INFO] [INFO] [INFO] Building A 1.0.0-SNAPSHOT [INFO] [INFO] [INFO] [INFO] Building B 1.0.0-SNAPSHOT [INFO] [INFO] [INFO] Reactor Summary: [INFO] [INFO] parent SUCCESS [0.003s] [INFO] A . SUCCESS [0.001s] [INFO] B . SUCCESS [0.002s] [INFO
Re: [maven] Re: Auto building parent and sibling projects as needed
Le 12/09/2011 15:33, Jason Pyeron a écrit : -Original Message- From: Guillaume Polet Sent: Monday, September 12, 2011 3:01 To: Maven Users List Subject: Re: [maven] Re: Auto building parent and sibling projects as needed Le 11/09/2011 17:37, Jason Pyeron a écrit : -Original Message- From: Guillaume Polet Sent: Sunday, September 11, 2011 4:07 To: Maven Users List Subject: [maven] Re: Auto building parent and sibling projects as needed The problem is that a child does not know where the sources of its parents are located, Is it not the point ofrelativePath../pom.xml/relativePath? No, this simply indicates where to look relatively to find a pom.xml if it is not installed in your local repository (or a remote one where it could be fetched from). Is this a design or bug of the reactor? It is by design. If you want to build a parent, then just go to the parent. If the parent build was triggered, you would not have any possibility to just build a child. and therefore it is completely unable to trigger its build. You probably have set up one or more parent aggregator projects and you mapped this hierarchy onto the file/directory structure but this is not mandatory at all. You can very well use a parent just to define the default version to use for dependencies, or the default target of the compiler, other properties that are common through all your projects and many more things. You should probably read again the first two paragraphs here: http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project snip/ Hard to say why your second build is failing. I just tried a similar setup and it worked in all cases: parent: The difference is that you are saying that the children A B are pom packaged, which does not cause compile to kick off, which inturn does not need the dependency. snip/ You can very well change them into jar's and add a dummy class in A and B project. It still works, I tried it myself. B: project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdtest/groupId artifactIdB/artifactId nameB/name version1.0.0-SNAPSHOT/version packagingpom/packaging parent groupIdtest/groupId artifactIdparent/artifactId version1.0.0-SNAPSHOT/version relativePath../pom.xml/relativePath snip/ Your log says the following: -- cannot find the pom.xml from project A (This I don't understand why) -- jar file of project A cannot be found Try 'mvn install' so that the pom and the jar file is deployed locally because it will not find the jar in the target directory. An install would not be appropiate for this part of the development lifecycle. For argument sake, lets assume that not every module passes all unit tests but all compile and we are in a SNAPSHOT versioning. -Jason OK, maybe some expert Maven user knows how to go around such a situation. AFIK (and my knowledge is not very big), you have two options: 1) You build the parent, the children will follow and you should be fine 2) You do an 'mvn install': since you are using SNAPSHOT it should not be a problem to have unstable jars (although using -DskipTest=true is not recommended, but that's another story) and since 'install' deploys the artifacts locally, you do not pollute anyone else's repository. Sorry if I can't help you more than that. Cheers, Guillaume -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: About transitive dependencies
Why do you declare a test (scope) dependency to B if you call it at runtime? AFIK, B should not be used when you compile C since you declared a test (scope) dependency. -- Guillaume Le 11/09/2011 08:25, JVerstry a écrit : I came across an issue I raised on StackOverflow: http://stackoverflow.com/questions/7373105/noclassdeffounderror-org-junit-afterclass-during-annotation-processing/7375380#7375380 I have a library B having a compile dependency (i.e. scope) on A. I have a library C having a test dependency (i.e. scope) on B. When I compile C, it includes B, but not A. And since C calls B calls A, it crashes at runtime. Apparently, this is how it should work according to the dependency scope (http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope). Yet, why should users of C explicitly declare a compile dependency to A, when we know at compile time that A will be required? Shouldn't the transitivity rule be that if you have such a transitive relationship, A should always be compile dependency of A? Or is there something I am missing? The problem is that the runtime crash is really late to be notified about this issue. It does not fit with the maven philosophy. Thanks, JVerstry - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Auto building parent and sibling projects as needed
The problem is that a child does not know where the sources of its parents are located, and therefore it is completely unable to trigger its build. You probably have set up one or more parent aggregator projects and you mapped this hierarchy onto the file/directory structure but this is not mandatory at all. You can very well use a parent just to define the default version to use for dependencies, or the default target of the compiler, other properties that are common through all your projects and many more things. You should probably read again the first two paragraphs here: http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance_vs_Project_Aggregation The first one explains the benefits of inheritance while the second explain the aggregation. Hope this helps you clear things out. Cheers, Guillaume Le 11/09/2011 06:21, Jason Pyeron a écrit : I am trying to understand why maven's reactor would not add a parent and a parent's children to the build when it is detected that the dependency is not in the repository. Is there a use case to NOT auto build? Or is there a technical hurdle to overcome to accomplish this in the reactor design? Could I be missing a concept on maven usage? I have a project which has a very large set of parent/child/sibling dependencies I am migrating from our ant build system. When an engineer needs to make changes on their part it would be best for them to execute mvn from that parts directory. -Jason -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trouble getting antrun plugin to run
I think you need to attach it to a phase:
execution
phasepackage/phase !-- for example here package--
...
/execution
Cheers,
Guillaume
Le 8/09/2011 19:01, laredotornado-3 a écrit :
Hi,
I'm using Maven 3.0.3. I have the below in thebuildplugins section of
my pom. However, when I run mvn clean deploy the echo message is never
printed out. Does anyone know why my antrun plugin isn't running?
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.6/version
executions
execution
phaseinstall/phase
configuration
echo message=Executing target /
condition property=is-release
not
contains string=${project.version} substring=SNAPSHOT/
/not
/condition
fail if=is-release message=You can only release snapshot versions of
this project./
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
Thanks, - Dave
--
View this message in context:
http://maven.40175.n5.nabble.com/Trouble-getting-antrun-plugin-to-run-tp4783208p4783208.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Clean Command
Use 'mvn clean package' instead of 'mvn package' Use 'mvn clean install' instead of 'mvn install' Use 'mvn clean deploy' instead of 'mvn deploy' Cheers, Guillaume Le 2/09/2011 16:56, anamika gupta a écrit : Hi, I need to clean my target folder every time i create the jar file or war file , can you please tell me what to write in pom.xml to do it. Any help is appreciated -- View this message in context: http://maven.40175.n5.nabble.com/Clean-Command-tp4762653p4762653.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Setting proxy information for Surefire
I think you are mixing two different aspects:
* Maven settings which are used by Maven and its plugin
* Your unit tests settings which you should set up yourself.
How do you make your tests work outside of Maven scope? In your IDE for
example? or manually? Do you pass your proxy settings using
-DhttpProxy.host and -DhttpProxy.port? If so, try to pass them to the
surefire configuration using this:
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#argLine
Cheers,
Guillaume
Le 2/09/2011 17:14, KARR, DAVID a écrit :
-Original Message-
From: KARR, DAVID
Sent: Friday, September 02, 2011 6:57 AM
To: Maven Users List
Subject: Setting proxy information for Surefire
I have an integration test run with Surefire using Spring's
SpringJUnit4ClassRunner. I have it loading my applicationContext.xml,
but it fails when it tries to load the schemas referenced in the
context. I've verified the schema exists at that URL. I can get it in
the browser and also with wget (proxy settings in my environment).
I have proxy settings in my settings.xml. I know they're correct
because mvn builds at the command line have downloaded many artifacts
from external repos.
Is there something maven-ish I should be configuring to get this to
work?
I tried adding this block to the plugin config:
systemProperties
property
nameHTTP_PROXY/name
value${env.HTTP_PROXY}/value
/property
/systemProperties
I verified that the HTTP_PROXY environment variable is a URL in the form
http://proxyhost:proxyport;. I use this same value as the http_proxy value
in my .wgetrc, and that works fine.
Unfortunately, this didn't fix my problem. It's still failing to get the
schema, and I've verified there is a schema at that URL.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced
For me, there are two strategies there: 1) You use the parent pom as an aggregator (your parent pom reference its children through modules) of several projects that always work together and make a coherent package--parent/children should keep the same version, it's just simpler to anyone's mind and simpler to maintain. 2) You use a parent pom to define well-defined practices, coherent set of dependencies, general properties used across all your projects, plugins and their configuration that you don't want to repeat in all your projects, but the parent does not know about its children--Then children should necessarily follow your parent version Cheers, Guillaume Le 1/09/2011 06:57, Eric Kolotyluk a écrit : OK, seems the problem was some data inconsistency with some things pointing to 0.0.2-SNAPSHOT and other things still pointing to 0.0.1-SNAPSHOT What is the best practice for when you want to change the version of the parent POM, and have all the children follow? I'm trying to use managed dependencies as much as possible, but somehow that is not enough. Also, is there some simple way to remove all 0.0.1-SNAPSHOT artifacts from Nexus? Cheers, Eric On 2011-08-31 8:54 PM, Eric Kolotyluk wrote: Is it just me, or does anyone else ever get tired of the message resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced Everything was working fine yesterday. For some reason, that I cannot explain, now my builds keep failing with this symptom. I have not actually changed any pom files or really anything - other than to stop and restart Eclipse. The same problem happens whether I build from Eclipse or the command line. I cannot seem to find any combination of '-U' or 'clean' or 'deploy' or anything to correct things. I feel like a chicken who pecks randomly at things until one of them is food. It is really unnerving that maven is so fragile and unpredictable, and things so randomly go from working to broken. While Maven is way better than Ant in most respects, Ant is still head and shoulders above Maven in stability. [ERROR] Failed to execute goal on project intersystem-jni4net: Could not resolve dependencies for project com.kodak.intersystem:intersystem-jni4net:jar:0.0.2-SNAPSHOT: The following artifacts could not be resolved: com.kodak.intersystem:intersystem-common:jar:0.0.2-SNAPSHOT, com.kodak.intersystem:intersystem-client:jar:0.0.2-SNAPSHOT, com.kodak.intersystem:intersystem-service:jar:0.0.2-SNAPSHOT, com.kodak.intersystem:color-repository:jar:0.0.2-SNAPSHOT: Failure to find com.kodak.intersystem:intersystem-common:jar:0.0.2-SNAPSHOT in http://nexus:8081/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced - [Help 1] When I look in my local repository I can see intersystem-common-0.0.2-SNAPSHOT.jar.lastUpdated intersystem-common-0.0.2-SNAPSHOT.pom.lastUpdated but intersystem-common-0.0.2-SNAPSHOT.jar intersystem-common-0.0.2-SNAPSHOT.pom are missing. Why is that when the previous 'deploy' succeeded? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: web application problem
As far as I can see, this is not really related to Maven but rather to the Google Eclipse Plugin. Have you tried creating a launch configuration from the menu? -- Guillaume Le 1/09/2011 14:19, Luka Stopar a écrit : Greetings! I'm having a problem using gwt-maven-plugin. The project compiles fine, but I cannot run it as a web application, I can only run it by doing run as-maven build...-gwt:run, in which case I cannot debug the code. I've attached my pom.xml, it may not look best, because I already did some trial and error. Cheers Luka - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: web application problem
Ok, it's been a while since I launched a GWT-app, but here are few pointers: * Make sure your project has the appropriate natures (see .project file):natureorg.eclipse.jdt.core.javanature/nature and naturecom.google.gwt.eclipse.core.gwtNature/nature * Make sure Google can find your modules/entry points--Select your project, right click--Properties. Go to Google--Web Toolkit * Make sure you have set the war directory properly--Select your project, right click--Properties. Go to Google--Web Application: Check the this project has a war directory, set the war directory to the appropriate value (usually src/main/webapp) -- Guillaume Le 1/09/2011 14:27, Luka Stopar a écrit : Yes I have, but the GWT tab is disabled and the run button also On 09/01/2011 02:24 PM, Guillaume Polet wrote: As far as I can see, this is not really related to Maven but rather to the Google Eclipse Plugin. Have you tried creating a launch configuration from the menu? -- Guillaume Le 1/09/2011 14:19, Luka Stopar a écrit : Greetings! I'm having a problem using gwt-maven-plugin. The project compiles fine, but I cannot run it as a web application, I can only run it by doing run as-maven build...-gwt:run, in which case I cannot debug the code. I've attached my pom.xml, it may not look best, because I already did some trial and error. Cheers Luka - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced
Well, it also aggregates your whole build together. If you do an 'mvn package' on your parent project, it will package your parent and all its children. If you don't define the modules in your parent, doing an 'mvn package' will only result in the packaging of your parent pom. Guillaume Le 1/09/2011 16:28, Eric Kolotyluk a écrit : OK, I think I am strategy (1) - although the only thing the parent actually agrregates is the javadoc. Or does aggregator have another meaning here? Is there some way I can set things up so that I only have to change the parent version and the children will all follow. The problem I ran into is that the child POMs contain the version for the parent (and the problem was they did not match), Can this be removed so the children just assume the parent version? Cheers, Eric On Thu, Sep 1, 2011 at 12:59 AM, Guillaume Polet guillaume.po...@gmail.comwrote: For me, there are two strategies there: 1) You use the parent pom as an aggregator (your parent pom reference its children through modules) of several projects that always work together and make a coherent package--parent/children should keep the same version, it's just simpler to anyone's mind and simpler to maintain. 2) You use a parent pom to define well-defined practices, coherent set of dependencies, general properties used across all your projects, plugins and their configuration that you don't want to repeat in all your projects, but the parent does not know about its children--Then children should necessarily follow your parent version Cheers, Guillaume Le 1/09/2011 06:57, Eric Kolotyluk a écrit : OK, seems the problem was some data inconsistency with some things pointing to 0.0.2-SNAPSHOT and other things still pointing to 0.0.1-SNAPSHOT What is the best practice for when you want to change the version of the parent POM, and have all the children follow? I'm trying to use managed dependencies as much as possible, but somehow that is not enough. Also, is there some simple way to remove all 0.0.1-SNAPSHOT artifacts from Nexus? Cheers, Eric On 2011-08-31 8:54 PM, Eric Kolotyluk wrote: Is it just me, or does anyone else ever get tired of the message resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced Everything was working fine yesterday. For some reason, that I cannot explain, now my builds keep failing with this symptom. I have not actually changed any pom files or really anything - other than to stop and restart Eclipse. The same problem happens whether I build from Eclipse or the command line. I cannot seem to find any combination of '-U' or 'clean' or 'deploy' or anything to correct things. I feel like a chicken who pecks randomly at things until one of them is food. It is really unnerving that maven is so fragile and unpredictable, and things so randomly go from working to broken. While Maven is way better than Ant in most respects, Ant is still head and shoulders above Maven in stability. [ERROR] Failed to execute goal on project intersystem-jni4net: Could not resolve dependencies for project com.kodak.intersystem:** intersystem-jni4net:jar:0.0.2-**SNAPSHOT: The following artifacts could not be resolved: com.kodak.intersystem:**intersystem-common:jar:0.0.2-**SNAPSHOT, com.kodak.intersystem:**intersystem-client:jar:0.0.2-**SNAPSHOT, com.kodak.intersystem:**intersystem-service:jar:0.0.2-**SNAPSHOT, com.kodak.intersystem:color-**repository:jar:0.0.2-SNAPSHOT: Failure to find com.kodak.intersystem:**intersystem-common:jar:0.0.2-**SNAPSHOT in http://nexus:8081/nexus/**content/groups/publichttp://nexus:8081/nexus/content/groups/publicwas cached in the local repository, resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced - [Help 1] When I look in my local repository I can see intersystem-common-0.0.2-**SNAPSHOT.jar.lastUpdated intersystem-common-0.0.2-**SNAPSHOT.pom.lastUpdated but intersystem-common-0.0.2-**SNAPSHOT.jar intersystem-common-0.0.2-**SNAPSHOT.pom are missing. Why is that when the previous 'deploy' succeeded? --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced
Le 1/09/2011 16:45, Eric Kolotyluk a écrit : Interesting - thanks for sharing that. At the moment I do not really need to change versions, I was experimenting to see if I could understand the process. Do I have the following ideas right? 1. I changed my version from 0.0.1-SNAPSHOT to 0.0.2-SNAPSHOT as a test to see what happens. Since I have not actually done a release, then technically I really do not need to increment the version. Yes indeed, this is not needed. Once you have created a release, requests for the snapshot will be answered with the release version and it is strongly discouraged to overwrite a release. 2. Would the normal practice be to: - Perform a mvn release - Create a new SCM branch from the current release on the main branch - Increment the version(s) on the main branch That would be my way to do it. 3. Or would it be better to: - Create a new SCM branch from main - Perform a mvn release from the new branch - Increment the version(s) on the main branch That would not be my way to do it, but I guess this is as valid. 4. In my case I have less than a dozen modules and they are tightly related, so I want all the versions to match the parent. It would be nice if I could just change the version of the parent POM and have everything fall out from there, but I seem to have to change it elsewhere too. Maven release is your friend there: on multi-module projects, you can ask to move all version to the same new one. If you do this manually, then yes, there is no alternative but to modify all pom's file. Cheers, Eric Guillaume On Thu, Sep 1, 2011 at 6:26 AM, Ron Wheeler rwhee...@artifact-software.comwrote: We started by changing the version of every module but eventually went to a policy of only changing the versions of modules that changed. The project was a portal with 70+ modules so it was a PITA to change all the versions. Not a big project overhead but we got tired of it and once we had moved much of the architecture to SOA with Web Services, it became clear that in a new release of the portal, most of the modules did not actually change. We then just reversioned the changed modules, produced a new parent version and a new version of the core modules that dealt with the persistence since the database had changed. We used a simple spreadsheet to document the versions of the modules that were required to build the new version of the portal. Made our lives a lot simpler and we started to think of our own code in the same way that we viewed third party libraries - if we did not need to upgrade to fix a bug or get new functionality then we left the old version intact. This obviously had a lot of benefits in testing and reduction of useless builds. We did not use the parent for managing the versions of dependencies in the modules since we had a better scheme for managing that. Ron On 01/09/2011 3:59 AM, Guillaume Polet wrote: For me, there are two strategies there: 1) You use the parent pom as an aggregator (your parent pom reference its children through modules) of several projects that always work together and make a coherent package--parent/children should keep the same version, it's just simpler to anyone's mind and simpler to maintain. 2) You use a parent pom to define well-defined practices, coherent set of dependencies, general properties used across all your projects, plugins and their configuration that you don't want to repeat in all your projects, but the parent does not know about its children--Then children should necessarily follow your parent version Cheers, Guillaume Le 1/09/2011 06:57, Eric Kolotyluk a écrit : OK, seems the problem was some data inconsistency with some things pointing to 0.0.2-SNAPSHOT and other things still pointing to 0.0.1-SNAPSHOT What is the best practice for when you want to change the version of the parent POM, and have all the children follow? I'm trying to use managed dependencies as much as possible, but somehow that is not enough. Also, is there some simple way to remove all 0.0.1-SNAPSHOT artifacts from Nexus? Cheers, Eric On 2011-08-31 8:54 PM, Eric Kolotyluk wrote: Is it just me, or does anyone else ever get tired of the message resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced Everything was working fine yesterday. For some reason, that I cannot explain, now my builds keep failing with this symptom. I have not actually changed any pom files or really anything - other than to stop and restart Eclipse. The same problem happens whether I build from Eclipse or the command line. I cannot seem to find any combination of '-U' or 'clean' or 'deploy' or anything to correct things. I feel like a chicken who pecks randomly at things until one of them is food. It is really unnerving that maven is so fragile and unpredictable, and things so randomly go from working to broken. While
Re: Error running Maven Tests with powermock and junit
Does your class containing the tests matches the default include patterns? http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#includes includes include**/Test*.java/include include**/*Test.java/include include**/*TestCase.java/include /includes Guillaume Le 15/07/2011 15:51, Greg Akins a écrit : On Fri, Jul 15, 2011 at 9:44 AM, Chiarachiara_sime...@hotmail.it wrote: Hi, yes i've put all test under this folder. I don't know what to do seriously.. 'cause if i try to run test using run as junit tests it works.. So the only change you make.. after the JUnit tests run, is to add the @RunWith(PowerMockRunner.class) attribute? And then the tests are not recognized? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Assembly plugin
1) Use ${basedir}
2) Use the outputDirectory tag (see
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html)
Cheers
Guillaume
Le 12/07/2011 17:54, Timothy Mcginnis a écrit :
I have several questions about the assembly plugin and filtering with the
assembly plugin.
1) I would like to use thebaseDirectory value in the assembly.xml file
in one of the filtered files but I can't seem to get it to work. I have
tried several variations. I did put a ${project.version} in to make sure
filtering was working and this showed up as expected. I tried
${baseDirectory}
${assembly.baseDirectory}
${project.assembly.baseDirectory}
${project.baseDirectory}
${pom.baseDirectory}
${pom.assembly.baseDirectory}
2) I have a different assembly.xml where I only want to include one script
under a base directory. I want the zip file to contain the following:
MyBaseDirectory/myScript.bat
But all I get is a zip file with myScript.bat in it. Here is the
assembly.xml file. The script myScript.bat resides in the directory
batchscripts.
assembly xmlns=
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
http://maven.apache.org/xsd/assembly-1.1.2.xsd;
idbatchscripts/id
formats
formatzip/format
/formats
baseDirectoryMyBaseDirectory/baseDirectory
fileSets
fileSet
directorybatchscripts/directory
filteredtrue/filtered
/fileSet
/fileSets
/assembly
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
==
This message contains privileged and confidential information intended for the
above addressees only. If you
receive this message in error please delete or destroy this message and/or
attachments.
The sender of this message will fully cooperate in the civil and criminal
prosecution of any individual engaging
in the unauthorized use of this message.
==
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Maven ant run: Reference maven.plugin.classpath not found.
Hi List,
I know that this question has been asked several times, but after
googling a bit, I could not find any solution to my error.
I am using maven ant-run plugin to execute a ant file. Here is what my
build section looks like:
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
version1.6/version
executions
execution
idbuild/id
phasepackage/phase
configuration
target
ant inheritRefs=true inheritall=true antfile=build.xml
target=deploy /
/target
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdorg.apache.maven/groupId
artifactIdmaven-ant-tasks/artifactId
version2.1.3/version
/dependency
/dependencies
/plugin
/plugins
Within my ant file, I have declared the following:
project name=project default=package basedir=.
xmlns:artifact=antlib:org.apache.maven.artifact.ant
...
typedef resource=org/apache/maven/artifact/ant/antlib.xml
uri=antlib:org.apache.maven.artifact.ant
classpathref=maven.plugin.classpath/
...
/project
And when I run ´mvn clean install´, I constantly get an error: Reference
maven.plugin.classpath not found.
I have tried using an embedded classpath tag instead of the classpathref
attribute. I can't get it to work. I saw a few solutions using a file
based classpathrefs, but I would rather not do that since it would imply
that I would have to maintain the dependencies of the additional Ant
tasks myself, which I am quite reluctant to do.
I have attached a simple project that reproduce my error.
Cheers,
Guillaume
P.S: I know that it is weird to use maven ant tasks within a maven
build, but I got my reasons.
project name=project default=package basedir=. xmlns:artifact=antlib:org.apache.maven.artifact.ant
typedef resource=org/apache/maven/artifact/ant/antlib.xml uri=antlib:org.apache.maven.artifact.ant classpathref=maven.plugin.classpath /
target name=package
artifact:dependencies filesetId=maven.artifact addArtifactFileSetRefs=true
dependency groupId=jdom artifactId=jdom version=1.1 type=jar /
/artifact:dependencies
copy todir=${basedir}/tmp
fileset refid=jdom:jdom:jar/
mapper type=flatten /
/copy
/target
/projectproject
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdtest/groupId
artifactIdtest/artifactId
packagingpom/packaging
version1.0-SNAPSHOT/version
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
version1.6/version
executions
execution
idbuild/id
phasepackage/phase
configuration
target
ant inheritRefs=true inheritall=true antfile=build.xml target=package /
/target
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdorg.apache.maven/groupId
artifactIdmaven-ant-tasks/artifactId
version2.1.3/version
/dependency
/dependencies
/plugin
/plugins
/build
/project
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Multimodule distribution
Hi, I have set up this kind of project by using Multi-module project; packages are built with the assembly plugin. The thing is that I have two main branches in my multi-module project: 1) for all the jars of code: this branch configures all the general presets for all jars of the application. 2) for all the different packages I want to create: this branch configures all the general presets for all packages I want to have. The Maven project structure looks like this: Root \---JARS | \---Core | \---Component A (Deps: Core) | \---Component B (Deps: Core) | \--- ... \---PACKAGES \--- PACKAGE 1 (Deps: Component A, Component B) \--- PACKAGE 2 (Deps: Component B, Component ...) \--- ... In the pom of PACKAGES, I have attached the maven assembly plugin to the build process (e.g. attached to the package phase). In each packages, I declare the correct dependencies that needs to be embedded in each package. The key for you will be to create a proper assembly descriptor file. Then if I use ´mvn clean install´ on the root pom and it builds all jars and then all packages. The bonus I get from such configuration is that I can use the Package pom's to create Launch configurations in development and I am then sure that it matches exactly what will be in each different package. Guillaume Le 11/07/2011 8:47, Ivan a écrit : Hello, guys! We have a project consisting of a main module (we call it core) and several configurable plugin modules (we call it component). By the application design each module is highly customizable and depends on one or more configuration files. When the application starts the conf folder is scanned and application configuration is constructed from all conf-files located in that folder. Depending on the usage scenario several combinations of configuration files may be used The basic aim we want to achieve is: 1) Have all possible configuration files stored in some folder of a module, e.g. for component A we have Aconf1.xml, Aconf2.xml and for component B Bconf1.xml and Bconf2.xml 2) For each target usage scenario we want to predefine a set of configuration files in a pom file that will build a distribution. E.g. for Scenario1 we should use Aconf1.xml and Bconf2.xml, but for Scenario2 we should use Aconf2.xml and Bconf1.xml 3) The resulting layout should look like ./lib - all *.jar files (core and components used) and ./conf - subset of configuration files specified in a distribution pom file. Can you suggest how this goal can be achieved with maven and distribution or assembly plugin? -- View this message in context: http://maven.40175.n5.nabble.com/Multimodule-distribution-tp4574067p4574067.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-resources-plugin - copying custom nonpackaged resources - rewrite existing files
Have you tried with the overwrite property in your resource plugin: http://maven.apache.org/plugins/maven-resources-plugin/resources-mojo.html#overwrite Yet your configuration seems kind of odd and not very robust if you cannot clean the output directory before packaging. One of the purpose of Maven is to have reproductible and consistent build. It seems that the way you manage your build is going in the opposite direction. Guillaume Le 7/07/2011 11:22, Dušan Rychnovský a écrit : Hi all, I use the maven-resources-plugin to copy some configuration files to the same directory as the resulting jar goes to (which is different from the standard target directory - I changed that using the maven-jar-plugin's outputDirectory configuration selection). It works fine, there's just one issue. If a file with the same name (but different content) already exists in the directory, maven won't copy the new version of the file (and thus rewrite the old one). I don't want to delete the whole directory before the copying phase, because there might be other files, which I don't won't to lose. I have searched google and it seems to me that it is not possible to configure the plugin the way I need. Please prove me wrong or advise me what is the best way to get the behaviour I need. I'm using maven version 2.2.1. Please excuse my improper english. Thanks a lot! Dusan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to set the parameter repositoryUrl in goal dependency:get ?
I have never tried this, but as I read the message of the plugin, it says The parameters 'repositoryUrl' for goal org.apache.maven.plugins:maven-dependecy-plugin:2.1:get are missing or invalid Looks to me that the value of repositoryUrl is not defined in your case, ie, the plugin does not perform a lookup on a system property named repositoryUrl I think that if you use -DrepoUrl='', it should work. Guillaume Le 7/07/2011 15:39, Gayard, Leonel a écrit : Hi, I'm trying to use the dependency plugin to fetch a single dependency: http://maven.apache.org/plugins/maven-dependency-plugin/get-mojo.html#repositoryUrl This is my command line: mvn -X dependency:get -DrepositoryUrl=some repo -Dartifact=org.apache.maven.plugins:maven-dependency-plugin:2.2:get I keep getting this error message: Caused by: org.apache.maven.plugin.PluginParameterException: The parameters 'repositoryUrl' for goal org.apache.maven.plugins:maven-dependecy-plugin:2.1:get are missing or invalid What's a valid repo url I can use ? For example, let's say I want to download the artifact from repo1.maven.org. Thanks, -- Leonel - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Import scope / Test scope and dependency management
The scope 'test' is not transitive. Therefore depending on ju-deps with
the scope test set on the junit dependency will not work in your case.
Guillaume
Le 1/07/2011 21:14, Luc De Graef a écrit :
Hello,
I have a problem with the import-scope dependency management (Maven 3.0.3).
There are 3 pom's involved.
The first is a 'ju-deps' dependency pom, merely used to encapsulate versions of
third party libs.
[code]
project
modelVersion4.0.0/modelVersion
groupIdcom.myself/groupId
artifactIdju-deps/artifactId
version1.0/version
packagingpom/packaging
nameju-deps/name
properties
junit.version4.8.1/junit.version
/properties
dependencies
!--- #1 : if one specifies the test scope in this dependency
pom, the test sources will not compile !!! --
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version${junit.version}/version
!--scopetest/scope--
/dependency
/dependencies
/project
[/code]
The second one is a parent project. In this project I use a dependency
management section (so that child projects do not need to specify a version).
I 'import' the ju-deps pom. Is this a correct scope?
[code]
project
modelVersion4.0.0/modelVersion
groupIdcom.myself/groupId
artifactIdparentapp/artifactId
packagingpom/packaging
version1.0/version
modules
modulesampleapp/module
/modules
dependencyManagement
dependencies
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
version1.1.1/version
/dependency
dependency
groupIdcom.myself/groupId
artifactIdju-deps/artifactId
version1.0/version
typepom/type
scopeimport/scope
/dependency
/dependencies
/dependencyManagement
/project
[/code]
The third one is a 'sampleapp' child project, that provides a test class (so it
needs a dependency to ju-deps).
[code]
project
modelVersion4.0.0/modelVersion
parent
groupIdcom.myself/groupId
artifactIdparentapp/artifactId
version1.0/version
/parent
artifactIdsampleapp/artifactId
dependencies
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
/dependency
!-- #2. If one specifies a pom inside
dependency management, one needs to give the version,
although the version was specified in the dependency
management section of the parent.
[ERROR] The
project com.myself:sampleapp:1.0 (D:\tryout\import\sampleapp\pom.xml) has 1
error
[ERROR]
'dependencies.dependency.version' for com.myself:ju-deps:pom is missing. @ line
16, column 21--
dependency
groupIdcom.myself/groupId
artifactIdju-deps/artifactId
!--version1.0/version--
typepom/type
scopetest/scope
/dependency
/dependencies
/project
[/code]
There are 2 problems (indicated in the pom source).
#1 : if one specifies a test scope in a dependency pom, the test sources in the
sampleapp child project do not get (test-)compiled correctly. This seems
something I can live with.
#2 : If one specifies a dependent pom in a child project, one needs to give the
version, although the version was specified in the dependency management
section of the parent. What am I doing wrong here?
Regards,
Luc
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: linking my own application jar file to my maven build.
The parent pom cannot be found, probably because it has never been installed in your local repository. Go to you hello-world-application directory and run 'mvn install'. (add the -N switch if you only want to build the parent pom and not the modules). Also in your parent pom, add a version number to compiler plugin. Guillaume Le 4/07/2011 8:04, samwun a écrit : Hello, I have created 2 applications: 1. hello-world-service 2. hello-world-service-impl And then I have created a hello-world-service.jar file for the hello-world-service package in my hello-world application. I have executed mvn install command, [code=java] sam@sam-PC /cygdrive/c/work/hello-world-start/hello-world-service $ mvn install [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for nl.devatwork.hello.world:hello-world-service:jar:1.0.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ nl.devatwork.hello.world:hello-world-application:1.0.0-SNAPSHOT, C:\work\hello-world-start\pom.xml, line 24, column 21 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] [INFO] Building Dev@Work Hello World Service Contract 1.0.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ hello-world-service --- [WARNING] Using platform encoding (GBK actually) to copy filtered resources, i.e. build is platform dependent! [INFO] Copying 0 resource [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ hello-world-service --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ hello-world-service --- [WARNING] Using platform encoding (GBK actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory C:\work\hello-world-start\hello-world-service\src\test\resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ hello-world-service --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.7.2:test (default-test) @ hello-world-service --- [INFO] No tests to run. [INFO] Surefire report directory: C:\work\hello-world-start\hello-world-service\target\surefire-reports --- T E S T S --- There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ hello-world-service --- [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ hello-world-service --- [INFO] Installing C:\work\hello-world-start\hello-world-service\target\hello-world-service-1.0.0-SNAPSHOT.jar to C:\maven\repository\nl\devatwork\hello\world\hello-world-service\1.0.0-SNAPSHOT\hello-world-service-1.0.0-SNAPSHOT.jar [INFO] Installing C:\work\hello-world-start\hello-world-service\pom.xml to C:\maven\repository\nl\devatwork\hello\world\hello-world-service\1.0.0-SNAPSHOT\hello-world-service-1.0.0-SNAPSHOT.pom [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 9.008s [INFO] Finished at: Mon Jul 04 14:34:05 EST 2011 [INFO] Final Memory: 4M/29M [INFO] [/code] It seems ok for building and installing the hello-world-service module. then having error when I tried to build hello-world-service-impl: [code=java]sam@sam-PC /cygdrive/c/work/hello-world-start/hello-world-service $ cd ../hello-world-service-impl/ sam@sam-PC /cygdrive/c/work/hello-world-start/hello-world-service-impl $ mvn clean package [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for nl.devatwork.hello.world:hello-world-service-impl:war:1.0.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ nl.devatwork.hello.world:hello-world-application:1.0.0-SNAPSHOT, C:\work\hello-world-start\pom.xml, line 24, column 21 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] [INFO] Building Dev@Work
Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project
It's an M2Eclipse problem. I think you should rather user their ML. -- Guillaume Le 29/06/2011 17:15, Sebastian Goldt a écrit : Hi all, today, I run into some problems with the Maven Eclipse Plugin 2.8 using Maven 3.0.3 on an Ubuntu 11.04 while setting up a mixed Java / Groovy project. It seems as if the eclipse plugin doesn't include all source code folders in the generated .project file. I haven't found anything on the internet on that particular issue so far... *Details:* My project in question contains both tests and main source code in java as well as in groovy, so I have the four folders src/main/java, src/main/groovy, src/test/java and src/test/groovy which are added to the project with the Build Helper Maven Plugin (1.6). When I generate the eclipse project files using eclipse:eclipse, the generated .classpath file only contains the src/main/groovy folder and not the src/test/groovy folder. *Reproduction:* The easiest way to reproduce the problem is by using a java/groovy project quickstarter from codehaus: 1. Create a dummy groovy/java project by using typing: mvn archetype:generate -DarchetypeGroupId=org.codehaus.groovy -DarchetypeArtifactId=groovy-eclipse-quickstart -DarchetypeVersion=2.5.1-M3-SNAPSHOT -DgroupId=foo -DartifactId=bar -Dversion=1 -DinteractiveMode=false -DarchetypeRepository= https://nexus.codehaus.org/content/repositories/snapshots/ 2. Create Eclipse project files mvn eclipse:eclipse When inspecting the generated .classpath file, you will notice that the src/test/groovy path is missing. Note that if you wanted to import the project into eclipse, you would have to set up the eclipse plugin in your pom as to include *.groovy classes on your build path and properly organise the files in packages; however, this wouldn't change the actual problem in any way. *Workaround:* Simply import the project into Eclipse and declare the src/test/groovy folder as source folder. Is this a bug or is there another mistake? Regards, Sebastian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn assembly:single with distribution child module
Actually, I would simply have added the profile in the child module and activate it through some system property on the command-line: mvn -Dbuild.dist=true package profiles profile iddist/id activation property namebuild.dist/name /property /activation build plugins plugin artifactIdmaven-assembly-plugin/artifactId version2.2.1/version configuration descriptorRefs descriptorRefjar-with-dependencies/descriptorRef /descriptorRefs /configuration executions execution idmake-assembly/id phasepackage/phase goals goalsingle/goal /goals /execution /executions /plugin /plugins /build /profile /profiles Guillaume Le 28/06/2011 1:33, Anders Hammar a écrit : No, you shouldn't be doing that in the parent project. As the parent project needs to be built before the children, it will not work (or will require some workaround). The profile you have is what I would suggest. Or, maybe even keep this module outside of the build all together as a separate project which you only build on demand (or have CI build every now and then). /Anders On Mon, Jun 27, 2011 at 16:50, Jean-Pierre Bergaminja...@ractive.chwrote: Good point, thanks. I tried to only add the distribution child module for a given profile like this: profiles profile iddist/id modules moduledistribution_project/**module /modules /profile /profiles So the assembly plugin is only run when setting the dist profile like: mvn -P dist package This would be a possible solution. But I still would expect that simply calling mvn assembly:single from the parent should work or that there are simpler solutions. Best regards, James Am 27.06.2011 16:26, schrieb Guillaume Polet: Could'nt you use a profile for that purpose? http://maven.apache.org/**guides/introduction/** introduction-to-profiles.htmlhttp://maven.apache.org/guides/introduction/introduction-to-profiles.html Cheers, Guillaume Le 27/06/2011 16:23, Jean-Pierre Bergamin a écrit : Hello maven users We are using the maven assembly plugin to copy all generated modules and dependencies to one central folder. For this we created a dedicated child module that used the assembly plugin as desribed in the FAQ (http://maven.apache.org/**plugins/maven-assembly-plugin/** faq.html#module-binarieshttp://maven.apache.org/plugins/maven-assembly-plugin/faq.html#module-binaries ). The assembly:single goal is executed in the package phase at the moment. Because it always takes quite a while for the assembly package to run, we do not want to execute it in the package phase by default anymore, but only on request by the user. Now is there a way to execute the assembly:single goal from the parent project explicitely? When assembly:single goal is executed in the package phase, it works. When I try to execute mvn assembly:single from the parent without having it run in the package phase, I get the error: [ERROR] Failed to execute goal org.apache.maven.plugins:**maven-assembly-plugin:2.2-**beta-5:single (default-cli) on project eranger: Error reading assemblies: No assembly descriptors found. - [Help 1] Any ideas how the assembly:single can be called explicitely? Best regards, James --**--** - To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Resources inclusion/exclusion patterns
Hi All, I am working on a project were I would like to exclude all resources except the ones located within META-INF. After reading carefuly the documentation, it appears that excludes always beats includes, so doing what would only be natural, does not work: build resources resource directorysrc/main/resources/directory excludes exclude**/*/exclude /excludes includes includeMETA-INF/**/*/include /includes /resource /resources ... /build So my second guess was to do the following: build resources resource directorysrc/main/resources/directory includes includeMETA-INF/**/*/include /includes /resource /resources ... /build but still not what I want because I end up with everything. -- what is the purpose of include patterns, if they embed everything anyway? Is there a way to do what I want without having to use an additional resource directory? My configuration details : Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: D:\apache-maven-3.0.3\bin\.. Java version: 1.6.0_16, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_16\jre Default locale: fr_BE, platform encoding: Cp1252 OS name: windows xp, version: 5.1, arch: x86, family: windows Many thanks, Guillaume
Re: Resources inclusion/exclusion patterns
Ok, sorry about that but I did not see my e-mails coming back to my posting address so I thought the e-mails had been blacklisted for some reason; I didn't know that we don't receive the e-mails we send to the ML. For the second part, I do want my files within META-INF to be embedded in my final package. However, the ones that are next to my META-INF directory should not be included and I was unable to perform this so far. It just seems that my inclusion pattern is not considered and it embeds everything anyway although I specifically indicated to embed only META-INF/**/*. Again sorry for the spam, it was never my intent to flood the ML. Cheers, Guillaume Le 27/06/2011 10:50, Stephen Connolly a écrit : Please stop reposting the same question in a different thread. This is not the way to get attention... even just replying to your initial question would be better. Includes are applied first followed by excludes to trim out the stuff you added in the includes... If you don't specify includes, the default is to include everything. I'm not seeing your problem myself... if you don't want the files to be included, then don't put the files in src/main/resources/META-INF in the first place if they are test resources, you should be putting them in src/test/resources/META-INF and that way they won't end up in the jar. if they are required files in META-INF, e.g. META-INF/MANIFEST.MF then don't create a jar create a zip instead (hint maven assembly plugin) -Stephen On 27 June 2011 09:21, Guillaume Poletmacha...@hotmail.com wrote: Hi All, I am working on a project were I would like to exclude all resources except the ones located within META-INF. After reading carefuly the documentation, it appears that excludes always beats includes, so doing what would only be natural, does not work: build resources resource directorysrc/main/resources/directory excludes exclude**/*/exclude /excludes includes includeMETA-INF/**/*/include /includes /resource /resources ... /build So my second guess was to do the following: build resources resource directorysrc/main/resources/directory includes includeMETA-INF/**/*/include /includes /resource /resources ... /build but still not what I want because I end up with everything. -- what is the purpose of include patterns, if they embed everything anyway? Is there a way to do what I want without having to use an additional resource directory? My configuration details : Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: D:\apache-maven-3.0.3\bin\.. Java version: 1.6.0_16, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_16\jre Default locale: fr_BE, platform encoding: Cp1252 OS name: windows xp, version: 5.1, arch: x86, family: windows Many thanks, Guillaume - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Resources inclusion/exclusion patterns
Indeed, this is probably what we should do, but yet (for some probably poor reason) I would like to keep everything in the same folder (actually the other resources will be embedded in an additional artifact created with Maven assembly). My only question is why do I get everything when I use the following patterns build resources resource directorysrc/main/resources/directory includes includeMETA-INF/**/*/include /includes /resource /resources ... /build while according to what you said, this should not be the case? Anyway, I found the solution to my problem (although I hardly understand why I get the expected result) but using : resources resource directorysrc/main/resources/directory excludes exclude**/*/exclude /excludes /resource resource directorysrc/main/resources/directory includes includeMETA-INF/**/*/include /includes /resource /resources gives me exactly what I expected. -- Guillaume Le 27/06/2011 10:58, Stephen Connolly a écrit : If they are files that are not needed in the final package, don't keep them in src/main/resources On 27 June 2011 09:56, Guillaume Poletguillaume.po...@gmail.com wrote: Ok, sorry about that but I did not see my e-mails coming back to my posting address so I thought the e-mails had been blacklisted for some reason; I didn't know that we don't receive the e-mails we send to the ML. For the second part, I do want my files within META-INF to be embedded in my final package. However, the ones that are next to my META-INF directory should not be included and I was unable to perform this so far. It just seems that my inclusion pattern is not considered and it embeds everything anyway although I specifically indicated to embed only META-INF/**/*. Again sorry for the spam, it was never my intent to flood the ML. Cheers, Guillaume Le 27/06/2011 10:50, Stephen Connolly a écrit : Please stop reposting the same question in a different thread. This is not the way to get attention... even just replying to your initial question would be better. Includes are applied first followed by excludes to trim out the stuff you added in the includes... If you don't specify includes, the default is to include everything. I'm not seeing your problem myself... if you don't want the files to be included, then don't put the files in src/main/resources/META-INF in the first place if they are test resources, you should be putting them in src/test/resources/META-INF and that way they won't end up in the jar. if they are required files in META-INF, e.g. META-INF/MANIFEST.MF then don't create a jar create a zip instead (hint maven assembly plugin) -Stephen On 27 June 2011 09:21, Guillaume Poletmacha...@hotmail.comwrote: Hi All, I am working on a project were I would like to exclude all resources except the ones located within META-INF. After reading carefuly the documentation, it appears that excludes always beats includes, so doing what would only be natural, does not work: build resources resource directorysrc/main/resources/directory excludes exclude**/*/exclude /excludes includes includeMETA-INF/**/*/include /includes /resource /resources ... /build So my second guess was to do the following: build resources resource directorysrc/main/resources/directory includes includeMETA-INF/**/*/include /includes /resource /resources ... /build but still not what I want because I end up with everything. -- what is the purpose of include patterns, if they embed everything anyway? Is there a way to do what I want without having to use an additional resource directory? My configuration details : Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: D:\apache-maven-3.0.3\bin\.. Java version: 1.6.0_16, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_16\jre Default locale: fr_BE, platform encoding: Cp1252 OS name: windows xp, version: 5.1, arch: x86, family: windows Many thanks, Guillaume - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn assembly:single with distribution child module
Could'nt you use a profile for that purpose? http://maven.apache.org/guides/introduction/introduction-to-profiles.html Cheers, Guillaume Le 27/06/2011 16:23, Jean-Pierre Bergamin a écrit : Hello maven users We are using the maven assembly plugin to copy all generated modules and dependencies to one central folder. For this we created a dedicated child module that used the assembly plugin as desribed in the FAQ (http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#module-binaries). The assembly:single goal is executed in the package phase at the moment. Because it always takes quite a while for the assembly package to run, we do not want to execute it in the package phase by default anymore, but only on request by the user. Now is there a way to execute the assembly:single goal from the parent project explicitely? When assembly:single goal is executed in the package phase, it works. When I try to execute mvn assembly:single from the parent without having it run in the package phase, I get the error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single (default-cli) on project eranger: Error reading assemblies: No assembly descriptors found. - [Help 1] Any ideas how the assembly:single can be called explicitely? Best regards, James - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn assembly:single with distribution child module
From what I undesrtand of Maven (I am not completely new but I never
read the code and other insights of it), when you call mvn some-goal on
a multi-module project, it is equivalent to calling this goal on every
module of the project (in the reactor order of course). Hence, when you
call assembly:single on your parent project (btw, the root parent is
always the first module built), it is like you added maven assembly to
the build of all modules of the project and you want it to be used with
its default configuration.
I am not sure of the default configuration, but my guess is that it
looks for a default assembly descriptor which is not found-- this
causes your error.
Now, if you want, you can probably either configure maven-assembly not
to run for certain modules using the skipAssembly parameter or use
profiles to only execute when you want.
I am not sur at all, but I think that you can define the following
property ${assembly.skipAssembly} to true in your root project and
within the one you want to execute maven assembly, you override by
setting that property to false.
Then calling mvn assembly:single on your parent should skip
maven-assembly on all your project except the one you want.
in your root project:
properties
assembly.skipAssemblytrue/assembly.skipAssembly
/properties
and in your specific one:
properties
assembly.skipAssemblyfalse/assembly.skipAssembly
/properties
but I haven't tested this, so I am not sure it works.
Guillaume
Le 27/06/2011 16:50, Jean-Pierre Bergamin a écrit :
Good point, thanks. I tried to only add the distribution child module
for a given profile like this:
profiles
profile
iddist/id
modules
moduledistribution_project/module
/modules
/profile
/profiles
So the assembly plugin is only run when setting the dist profile like:
mvn -P dist package
This would be a possible solution.
But I still would expect that simply calling mvn assembly:single from
the parent should work or that there are simpler solutions.
Best regards,
James
Am 27.06.2011 16:26, schrieb Guillaume Polet:
Could'nt you use a profile for that purpose?
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Cheers,
Guillaume
Le 27/06/2011 16:23, Jean-Pierre Bergamin a écrit :
Hello maven users
We are using the maven assembly plugin to copy all generated modules
and dependencies to one central folder. For this we created a
dedicated child module that used the assembly plugin as desribed in
the FAQ
(http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#module-binaries).
The assembly:single goal is executed in the package phase at the
moment. Because it always takes quite a while for the assembly package
to run, we do not want to execute it in the package phase by default
anymore, but only on request by the user.
Now is there a way to execute the assembly:single goal from the parent
project explicitely? When assembly:single goal is executed in the
package phase, it works. When I try to execute mvn assembly:single
from the parent without having it run in the package phase, I get the
error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
(default-cli) on project eranger: Error reading assemblies: No
assembly descriptors found. - [Help 1]
Any ideas how the assembly:single can be called explicitely?
Best regards,
James
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Resources inclusion/exclusion patterns
Hi All, I am working on a project were I would like to exclude all resources except the ones located within META-INF. After reading carefuly the documentation, it appears that excludes always beats includes, so doing what would only be natural, does not work: build resources resource directorysrc/main/resources/directory excludes exclude**/*/exclude /excludes includes includeMETA-INF/**/*/include /includes /resource /resources ... /build So my second guess was to do the following: build resources resource directorysrc/main/resources/directory includes includeMETA-INF/**/*/include /includes /resource /resources ... /build but still not what I want because I end up with everything. -- what is the purpose of include patterns, if they embed everything anyway? Is there a way to do what I want without having to use an additional resource directory? My configuration details : Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: D:\apache-maven-3.0.3\bin\.. Java version: 1.6.0_16, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_16\jre Default locale: fr_BE, platform encoding: Cp1252 OS name: windows xp, version: 5.1, arch: x86, family: windows Many thanks, Guillaume - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Can't resolve libraries.
Hi, from your logs, it looks like access to the Internet is not working or at least not for Maven, since most of the missing dependencies are available on central. Would you have a proxy/firewall set up somewhere and forgot to put that in your settings? Or do you have a local firewall that would block all connections? Also, it looks like your Nexus installation is not working either, because it seems that the index cannot be found (or again, it cannot be reached by Maven). A few URL you can try that should work: http://repo1.maven.org/maven2/easyconf/easyconf/0.9.0/easyconf-0.9.0.jar http://localhost:8081/nexus/content/groups/public/easyconf/easyconf/0.9.0/easyconf-0.9.0.jar Hard to say more without your settings. Guillaume Le 22/06/2011 9:24, samwun a écrit : Hello, I imported a maven project, but it can't resolve the following libraries. I have local Nexus installed and connected to the internet. 11-6-22 下午05时17分09秒: Unable to update index for local|http://localhost:8081/nexus/content/groups/public 11-6-22 下午05时17分05秒: Updating index local|http://localhost:8081/nexus/content/groups/public 11-6-22 下午05时17分23秒: Refreshing [/ixsystems-registration/pom.xml] 11-6-22 下午05时17分46秒: Missing artifact easyconf:easyconf:jar:0.9.0:compile 11-6-22 下午05时17分46秒: Missing artifact struts:struts:jar:1.1:compile 11-6-22 下午05时17分46秒: Missing artifact commons-beanutils:commons-beanutils:jar:1.6.1:compile 11-6-22 下午05时17分46秒: Missing artifact struts:struts-legacy:jar:1.1:compile 11-6-22 下午05时17分46秒: Missing artifact commons-validator:commons-validator:jar:1.1.4:compile 11-6-22 下午05时17分46秒: Missing artifact oro:oro:jar:2.0.7:compile 11-6-22 下午05时17分46秒: Missing artifact javax.sql:jdbc-stdext:jar:2.0:compile 11-6-22 下午05时17分46秒: Missing artifact commons-configuration:commons-configuration:jar:1.1:compile 11-6-22 下午05时17分46秒: Missing artifact commons-collections:commons-collections:jar:3.1:compile 11-6-22 下午05时17分46秒: Missing artifact commons-lang:commons-lang:jar:2.0:compile 11-6-22 下午05时17分46秒: Missing artifact dom4j:dom4j:jar:1.4:compile 11-6-22 下午05时17分46秒: Missing artifact jaxen:jaxen:jar:1.0-FCS:compile 11-6-22 下午05时17分46秒: Missing artifact saxpath:saxpath:jar:1.0-FCS:compile 11-6-22 下午05时17分46秒: Missing artifact msv:msv:jar:20020414:compile 11-6-22 下午05时17分46秒: Missing artifact relaxngDatatype:relaxngDatatype:jar:20020414:compile 11-6-22 下午05时17分46秒: Missing artifact isorelax:isorelax:jar:20020414:compile 11-6-22 下午05时17分46秒: Missing artifact commons-digester:commons-digester:jar:1.6:compile 11-6-22 下午05时17分46秒: Missing artifact xerces:xercesImpl:jar:2.2.1:compile 11-6-22 下午05时17分46秒: Missing artifact xml-apis:xml-apis:jar:1.0.b2:compile 11-6-22 下午05时17分46秒: Missing artifact commons-beanutils:commons-beanutils-core:jar:1.7.0:compile 11-6-22 下午05时17分46秒: Missing artifact commons-beanutils:commons-beanutils-bean-collections:jar:1.7.0:compile 11-6-22 下午05时17分46秒: Missing artifact mx4j:mx4j-jmx:jar:2.1.1:compile 11-6-22 下午05时17分46秒: Missing artifact mx4j:mx4j-impl:jar:2.1.1:compile 11-6-22 下午05时17分46秒: Missing artifact portlet-api:portlet-api:jar:1.0:provided 11-6-22 下午05时17分46秒: Missing artifact org.aspectj:aspectjrt:jar:1.6.6:compile 11-6-22 下午05时17分46秒: Missing artifact javax.servlet:servlet-api:jar:2.5:provided 11-6-22 下午05时17分46秒: Missing artifact javax.portlet:portlet-api:jar:2.0:provided 11-6-22 下午05时17分46秒: Missing artifact javax.servlet:jstl:jar:1.2:compile 11-6-22 下午05时17分46秒: Missing artifact junit:junit:jar:4.7:test 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-core:jar:3.0.2.RELEASE:compile 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-asm:jar:3.0.2.RELEASE:compile 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-jdbc:jar:3.0.2.RELEASE:compile 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-beans:jar:3.0.2.RELEASE:compile 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-test:jar:3.0.2.RELEASE:test 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-context:jar:3.0.2.RELEASE:compile 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-expression:jar:3.0.2.RELEASE:compile 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-webmvc-portlet:jar:3.0.2.RELEASE:compile 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-web:jar:3.0.2.RELEASE:compile 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-webmvc:jar:3.0.2.RELEASE:compile 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-aop:jar:3.0.2.RELEASE:compile 11-6-22 下午05时17分46秒: Missing artifact aopalliance:aopalliance:jar:1.0:compile 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-aspects:jar:3.0.2.RELEASE:compile 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-context-support:jar:3.0.2.RELEASE:compile 11-6-22 下午05时17分46秒: Missing artifact org.springframework:spring-tx:jar:3.0.2.RELEASE:compile 11-6-22 下午05时17分46秒: Missing artifact
Resource inclusion/exclusion patterns--what's the usage of include patterns?
Hi All, I am working on a project were I would like to exclude all resources except the ones located within META-INF. After reading carefuly the documentation, it appears that excludes always beats includes, so doing what would only be natural, does not work: build resources resource directorysrc/main/resources/directory excludes exclude**/*/exclude /excludes includes includeMETA-INF/**/*/include /includes /resource /resources ... /build So my second guess was to do the following: build resources resource directorysrc/main/resources/directory includes includeMETA-INF/**/*/include /includes /resource /resources ... /build but still not what I want because I end up with everything. -- what is the purpose of include patterns, if they embed everything anyway? Is there a way to do what I want without having to use an additional resource directory? My configuration details : Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: D:\apache-maven-3.0.3\bin\.. Java version: 1.6.0_16, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_16\jre Default locale: fr_BE, platform encoding: Cp1252 OS name: windows xp, version: 5.1, arch: x86, family: windows - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Resource inclusion/exclusion patterns--what's the usage of include patterns?
Hi All, I am working on a project were I would like to exclude all resources except the ones located within META-INF. After reading carefuly the documentation, it appears that excludes always beats includes, so doing what would only be natural, does not work: build resources resource directorysrc/main/resources/directory excludes exclude**/*/exclude /excludes includes includeMETA-INF/**/*/include /includes /resource /resources ... /build So my second guess was to do the following: build resources resource directorysrc/main/resources/directory includes includeMETA-INF/**/*/include /includes /resource /resources ... /build but still not what I want because I end up with everything. -- what is the purpose of include patterns, if they embed everything anyway? Is there a way to do what I want without having to use an additional resource directory? My configuration details : Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: D:\apache-maven-3.0.3\bin\.. Java version: 1.6.0_16, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_16\jre Default locale: fr_BE, platform encoding: Cp1252 OS name: windows xp, version: 5.1, arch: x86, family: windows - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Assembling assemblies with exclude/include patterns
Hello, I'm kind of new to the assembly plugin but I'm starting to get some stuff out of it. However there is one trick I couldn't get to work so far, so I'm looking for some help on this. Here is my situation: I have a bunch of projects which all produce a jar file (without any resources, just classes) and a zip file containing all the resources (no classes, no jars). This works smoothly and I'm very happy of the output they each produce. On addition to that, I have four projects that are various combination of the projects mentionned above. What I would like to do is to have them produce a zip file with the following structure: all the resources (located in the zip previously created) of the projects they depend of at the top of the zip file, and within a lib directory, all the jars they depend of. To do this, I have added 2 dependecy sets: one to include all jars and place them in a lib directory, and one to unpack all my zips. I think I'm really close to a solution, but I have one problem, which is that all my classes are also included along the resources. It seems that the exclusion patterns donnot work with the second dependency set. Is there a way to get to what I would like, or is this simply not possible? Many thanks in advance Guillaume Polet My assembly descriptor for those four projects look like this: assembly idpackaging/id formats formatzip/format /formats includeBaseDirectoryfalse/includeBaseDirectory dependencySets dependencySet includes include*.jar/include /includes excludes exclude*.zip/exclude /excludes outputDirectorylib/outputDirectory /dependencySet dependencySet unpacktrue/unpack outputDirectory/outputDirectory includes include*.zip/include /includes excludes exclude*.jar/exclude /excludes unpackOptions excludes exclude*.class/exclude exclude**/*.class/exclude excludeMETA-INF/exclude /excludes /unpackOptions /dependencySet /dependencySets /assembly - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Assembling assemblies with exclude/include patterns
Ok, well, worry that I have bothered you because I found my issues since. Two stuffs were actually causing my problems: 1) My repository was somehow corrupted and there were two shared jars containing the same descriptor. The plugin was using an old one instead of the ones I was updating while trying to find a solution 2) the include/exclude patterns were incorrect and replacing *.jar by *:jar:* and *.zip by *:zip:* did the trick. This is a little bit confusing because the include/exclude patterns in the dependency sets are not the same as in filesets (which by the way is logical but the documentation does not really specify that they are different) I am just posting this so that if anyone run into the same issue, he can read the solution I have found. Guillaume Polet Guillaume Polet a écrit : Hello, I'm kind of new to the assembly plugin but I'm starting to get some stuff out of it. However there is one trick I couldn't get to work so far, so I'm looking for some help on this. Here is my situation: I have a bunch of projects which all produce a jar file (without any resources, just classes) and a zip file containing all the resources (no classes, no jars). This works smoothly and I'm very happy of the output they each produce. On addition to that, I have four projects that are various combination of the projects mentionned above. What I would like to do is to have them produce a zip file with the following structure: all the resources (located in the zip previously created) of the projects they depend of at the top of the zip file, and within a lib directory, all the jars they depend of. To do this, I have added 2 dependecy sets: one to include all jars and place them in a lib directory, and one to unpack all my zips. I think I'm really close to a solution, but I have one problem, which is that all my classes are also included along the resources. It seems that the exclusion patterns donnot work with the second dependency set. Is there a way to get to what I would like, or is this simply not possible? Many thanks in advance Guillaume Polet My assembly descriptor for those four projects look like this: assembly idpackaging/id formats formatzip/format /formats includeBaseDirectoryfalse/includeBaseDirectory dependencySets dependencySet includes include*.jar/include /includes excludes exclude*.zip/exclude /excludes outputDirectorylib/outputDirectory /dependencySet dependencySet unpacktrue/unpack outputDirectory/outputDirectory includes include*.zip/include /includes excludes exclude*.jar/exclude /excludes unpackOptions excludes exclude*.class/exclude exclude**/*.class/exclude excludeMETA-INF/exclude /excludes /unpackOptions /dependencySet /dependencySets /assembly - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
