Re: Maven compiler plugin 3.1 version release?
Thank you very much! I'll keep an eye for it in the Maven repo. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-compiler-plugin-3-1-version-release-tp5749035p5749297.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
Maven compiler plugin 3.1 version release?
We are running into this bug http://jira.codehaus.org/browse/MCOMPILER-187 while building the JBoss AS project https://github.com/jbossas/jboss-as. That bug causes a extremely slow (re)build time for local dev environments, because it recompiles the entire Maven module every time there's a tiny change somewhere. That bug is marked as fixed for 3.1. Would it be possible to do a release of that plugin containing a bug fix, so that we can upgrade to that version? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-compiler-plugin-3-1-version-release-tp5749035.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: Issue with release plug-in copying incorrect scm path to create tag
This looks related to http://jira.codehaus.org/browse/MRELEASE-526 -- View this message in context: http://n2.nabble.com/Issue-with-release-plug-in-copying-incorrect-scm-path-to-create-tag-tp4857506p4857770.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: Optionally disable transitive dependencies in Maven
I would have done that. But the project B is not in my control. It's a third party project. Stevo Slavić wrote: > > I'd suggest that you refactor projectB bits used by both projectB and > projectA into a new projectC module and have it referenced as dependency > from both projectA and projectB. > > Regards, > Stevo. > > -- View this message in context: http://n2.nabble.com/Optionally-disable-transitive-dependencies-in-Maven-tp4259924p4260065.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
Optionally disable transitive dependencies in Maven
Hello everyone, I am using Maven-2.0.9 and I have a project A which depends on a couple of classes from project B. So obviously, i have a dependency in my pom.xml as follows: org projectB But the project B has a long list of transitive dependencies, none of which are required in project A. I was looking for a way to disable those transitive dependencies from being pulled into project A. One option would be to add numerous "exclude" elements to the dependency. But this is not practical, given the long list of transitive dependencies. I was looking for something like the following: org projectB false A "transitive" child element to the dependency element which can then be configured to disable transitive dependencies from being pulled in. From what i learn based on my discussion about this on #maven IRC, there's no technical reason why this can't be done/allowed. It would be useful to have this feature in Maven to disable transitive dependencies. Any thoughts? P.S: Is this the right list or should this be in maven-dev list? -- View this message in context: http://n2.nabble.com/Optionally-disable-transitive-dependencies-in-Maven-tp4259924p4259924.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: Maven assembler plugin - How to avoid duplicating configurations in assembler descriptors?
Excellent! Thanks for the quick response - i had been trying a lot of different ways of doing this, since this morning :) -Jaikiran Stevo Slavic wrote: > > http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/using-components.html > > Regards, > Stevo. > -- View this message in context: http://www.nabble.com/Maven-assembler-plugin---How-to-avoid-duplicating-configurations-in-assembler-descriptors--tp25821854p25822200.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
Maven assembler plugin - How to avoid duplicating configurations in assembler descriptors?
Hello everyone,
I have a project org.myapp:proj which is a jar artifact. This project is
configured to use maven-assembler-plugin to create a custom artifact (let's
say proj-client1.jar). The descriptor configuration xml (let's call it
client1-assembler.xml) used for this assembler plugin looks like this:
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/assembly-1.0.0.xsd";
>
clien1
jar
false
src/main/resources
blah.xml
packages
${artifactId}.${extension}
ant-contrib:ant-contrib
org.myapp.abc:xyz:jar
Now for this same project i need to generate another artifact
proj-client2.jar which does the exact same thing as the descriptor in
client1 *and also* adds its own set of libraries in the resultant artifact.
So a very simple way to achieve this would be to copy-paste the contents of
the client1-assembler.xml and create a client2-assembler.xml. The
client2-assembler.xml will then also have its own custom configurations. The
assembler plugin can then use this as:
maven-assembly-plugin
2.2-beta-1
make-assembly
package
single
src/main/resources/client1-assembler.xml
src/main/resources/client2-assembler.xml
However, copy/paste from client1-assembler.xml to client2-assembler.xml just
leads to duplicacy and maintenance nightmare (someone would have to ensure
that whatever changes happen to client1-assembler.xml is applied manually
even to client2-assembler.xml).
Is there a way i can avoid this duplicacy? Something on the lines of
client2-assembler.xml "referencing" or "inheriting" from
client1-assembler.xml. Is this possible or anything similar?
--
View this message in context:
http://www.nabble.com/Maven-assembler-plugin---How-to-avoid-duplicating-configurations-in-assembler-descriptors--tp25821854p25821854.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: LATEST version of an "artifact"
Wayne Fay wrote: > > As that book is a product of Sonatype, you will need to file a defect > in the Sonatype JIRA and it will probably be resolved in the next > "release" of the book. I don't have a link, but surely there is one at > www.sonatype.com. > > Wayne > Done, JIRA created https://issues.sonatype.org/browse/MVNDEF-112 -Jaikiran -- View this message in context: http://www.nabble.com/LATEST-version-of-an-%22artifact%22-tp24335281p24369049.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: LATEST version of an "artifact"
Thanks Stephen for explaining how the LATEST would have worked against artifacts. Would it be possible to update the documentation (the definitive guide) to make it clear that LATEST is meant for plugins? Right now, that doc contradicts the way LATEST behaves. -- View this message in context: http://www.nabble.com/LATEST-version-of-an-%22artifact%22-tp24335281p24359571.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: LATEST version of an "artifact"
Infact i get an error when i use LATEST: 1) org.myapp.abc:myapp-core:jar:LATEST Try downloading the file manually from the project website. Seems like LATEST isn't recognized as a valid qualifier? Jaikiran wrote: > > I am reading the Maven definitive guide > http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-pom-syntax.html > which says: > > "LATEST refers to the latest released or snapshot version of a particular > artifact..." > > Does this really work? I am using LATEST against a artifact, but i don't > seem to get it to use the latest available "snapshot" for that artifact. > It seems to look for the latest "released" artifact. I am using Maven > 2.0.9 > > > -- View this message in context: http://www.nabble.com/LATEST-version-of-an-%22artifact%22-tp24335281p24335445.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
LATEST version of an "artifact"
I am reading the Maven definitive guide http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-pom-syntax.html which says: "LATEST refers to the latest released or snapshot version of a particular artifact..." Does this really work? I am using LATEST against a artifact, but i don't seem to get it to use the latest available "snapshot" for that artifact. It seems to look for the latest "released" artifact. I am using Maven 2.0.9 -- View this message in context: http://www.nabble.com/LATEST-version-of-an-%22artifact%22-tp24335281p24335281.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 package phase for one subproject
As far as i know, you cannot skip the default lifecycle phases. Why exactly do you want to do this? -Jaikiran Marouane Amraoui-2 wrote: > > Hi, > I have a multiproject maven > > Parent1 : > > è Child1 > > è Child2 > > I launch mvn clean install on Parent1. > I need to skip package phase in subproject Child2. > > It is possible ? > > Thx in advance. > > -- View this message in context: http://www.nabble.com/Skip-package-phase-for-one-subproject-tp24269066p24274859.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: Scope
>From what i understand of the table here http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-transitive.html transitive dependencies for a "provided" scope dependencies are infact "provided". Are you seeing a different behaviour? -Jaikiran Sipungora wrote: > > Hi, > > I need provided transitive scope. Scope provided isn't transitive. Is > there a solution for it? > > Thanks in advance. > > > -- View this message in context: http://www.nabble.com/Scope-tp24270252p24274815.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
Custom dependency resolver for a Maven project
Hello everyone, I am trying to find some inputs on how best to manipulate the dependency resolution within Maven. Given a project X and its set of dependencies, is there a way wherein i can sort of filter out the dependencies? Or is there some documentation or any pointer on how to implement and configure/hook a custom dependency resolver? For example, if the project X depends on 1.0.0 version of xxx.yyy.zzz:someproject then is there some way where in i can modify this dependency (without actually modifying the dependency in the pom.xml) when the dependency resolution for the project is taking place? Also, which exact lifecycle phase does Maven do the dependency resolution for the project? And is the resolution done through some Maven plugin? Is it the same dependency plugin which is used for dependency:tree? -- View this message in context: http://www.nabble.com/Custom-dependency-resolver-for-a-Maven-project-tp24274681p24274681.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
Maven surefire plugin - testFailureIgnore and its behaviour with forkMode
I am using Maven surefire plugin 2.4.2 with the following configurations: maven-surefire-plugin ... false ... always ... I have intentionally set testFailureIgnore=false (i.e. the default value), so that if the test fails the build process fails. However when my tests fail with ERROR, i see that irrespective of this property value, the rest of the build is carried out and the build reports a SUCCESS. A bit of debugging and playing with the forkMode, shows that the testFailureIgnore=false results in the build to fail (which is what i expect) *only* when the forkMode is set to "never". Setting the forkMode to always or once always results in a successful build irrespective of the testFailureIgnore setting. Is this the expected behaviour? -- View this message in context: http://www.nabble.com/Maven-surefire-plugin---testFailureIgnore-and-its-behaviour-with-forkMode-tp22782458p22782458.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: Change the default output location of test resources
The reason why the resource:testResources is being run twice might be because > The goals that are configured will be added to the goals already bound to > the lifecycle from the packaging selected. > as documented in http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Plugins On the #maven IRC i did get some inputs about using an alternate approach: target/test-resources But i haven't yet been able to get this working. The target/test-resources is not created and the resources are not copied over. -- View this message in context: http://www.nabble.com/Change-the-default-output-location-of-test-resources-tp22097054p22119883.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
Change the default output location of test resources
I am using Maven-2.0.9 and trying to change the default output location of
the "test resources" (under src/test/resources). By default, they get copied
to target/tests-classes during mvn clean package. However, i want them to be
copied under my specific target/tests-resources folder. I followed the
maven-resources-plugin documentation and came up with this configuration in
my pom.xml:
org.apache.maven.plugins
maven-resources-plugin
2.3
change-test-resource-outputdir
process-test-resources
testResources
target/test-resources
This works in a weird way. Based on what i see, the test resources are
copied twice, once to the default location (target/tests-classes) and once
to my specific directory (target/tests-resources). Here's what i see on the
console:
[INFO] [enforcer:enforce {execution: enforce-banned-dependencies}]
[INFO] [resources:resources]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO] [compiler:compile]
[INFO] Compiling 7 source files to /home/myhome...
[INFO] [resources:testResources]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] Copying 4 resources
[INFO] [resources:testResources {execution: change-test-resource-outputdir}]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] Copying 4 resources
[INFO] [compiler:testCompile]
The resources:testResources seems to be called twice.
Is there any way i can avoid the tests resources from being copied to the
default output location?
--
View this message in context:
http://www.nabble.com/Change-the-default-output-location-of-test-resources-tp22097054p22097054.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How to import multi-module projects in Eclipse through mvn eclipse:eclipse
Thanks everyone for the inputs. Let me give the Eclipse plugin a try :) Eugene Kuleshov wrote: > > Rusty, > > The startup issue been fixed while ago. The project import and updating > dependencies may take some time for large project, but nothing like that > is happening at Eclipse startup anymore. > > regards, > Eugene > -- View this message in context: http://www.nabble.com/How-to-import-multi-module-projects-in-Eclipse-through-mvn-eclipse%3Aeclipse-tp21621731p21638772.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to import multi-module projects in Eclipse through mvn eclipse:eclipse
Kent Narling wrote: > > If you want to do this, why not use one of the maven eclipse plugins? > At least I know m2eclipse supports this very nicely... > The only reason i stay away from adding plugins (any plugins) to eclipse is because 1) It makes Eclipse slow 2) The plugins sometimes start off uncontrollable actions (ex: downloading dependencies etc...) But if that's the only way to do this, then maybe, i'll have to rethink. Isn't this supported from mvn plugins instead? -- View this message in context: http://www.nabble.com/How-to-import-multi-module-projects-in-Eclipse-through-mvn-eclipse%3Aeclipse-tp21621731p21622164.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
How to import multi-module projects in Eclipse through mvn eclipse:eclipse
I have a multiple module project with this parent pom containing this: myappone myapptwo The myappone and myapptwo have their own poms and are jar artifacts. From the top level parent i do a mvn eclipse:clean eclipse:eclipse And then from Eclipse (which does not have any plugins) i do a File -> Import -> Top level Project. At this point, i expected to see myappone and myapptwo availble for selection, in the list of projects to be selected. But i only see the top level parent in the selection. When i import this top level project, the child modules myappone and myapptwo are imported as resources for the top level project. As a result, whenever i want to traverse between the java classes of these projects (the "F3" way) i get a pop-up saying (The resource is not in build path). Is there a way through which i can import these child projects as java projects all at once from the top level instead of having to import them one at a time? -- View this message in context: http://www.nabble.com/How-to-import-multi-module-projects-in-Eclipse-through-mvn-eclipse%3Aeclipse-tp21621731p21621731.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: Getting log4j output from ANT tasks to maven output
ez wrote: > > instead i get this: > log4j:WARN No appenders could be found for logger > (com.i18n.Excel2Properties). > log4j:WARN Please initialize the log4j system properly. > The warning is because the log4j.properties or log4j.xml is not present in the classpath. Where have you placed it? -- View this message in context: http://www.nabble.com/Getting-log4j-output-from-ANT-tasks-to-maven-output-tp21558678p21598939.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: FW: Failed to resolve artifact
Varini H.P. wrote: > > > GroupId: org.apache.maven.plugins > ArtifactId: maven-compiler-plugin > Version: 2.0.2 > > Reason: Unable to download the artifact from any repository > > org.apache.maven.plugins:maven-compiler-plugin:pom:2.0.2 > > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > java.net (http://download.java.net/maven/1/) > Strange. I just tried accessing http://repo1.maven.org/maven2 and it automatically redirected me to http://repo2.maven.org/maven2 So try adding http://repo2.maven.org/maven2 to the list of repositories in your settings.xml -- View this message in context: http://www.nabble.com/FW%3A-Failed-to-resolve-artifact-tp21579179p21598922.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: Passing system properties to JUnit using "-D" on Linux
Being discussed here http://www.nabble.com/Passing-system-properties-to-JUnit-tests-using-%22-D%22-on-Linux-td21593651.html -- View this message in context: http://www.nabble.com/Passing-system-properties-to-JUnit-using-%22-D%22-on-Linux-tp21593649p21598861.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: Passing system properties to JUnit using "-D" on Linux
Being discussed in your other post here http://www.nabble.com/Passing-system-properties-to-JUnit-tests-using-%22-D%22-on-Linux-td21593651.html -- View this message in context: http://www.nabble.com/Passing-system-properties-to-JUnit-using-%22-D%22-on-Linux-tp21593647p21598856.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: Passing system properties to JUnit tests using "-D" on Linux
james_d wrote:
>
> However, I noticed that when I run my build on Linux that the properties
> are not available. Specifically, calling System.getProperty("key1")
> returns null. What's going on? I'm using maven 2.0.9 for both.
>
The OS shouldn't matter, it should have worked. Please post the exact
command that you are using and the piece of code where you using this
property. Also post the output of
mvn -version
--
View this message in context:
http://www.nabble.com/Passing-system-properties-to-JUnit-tests-using-%22-D%22-on-Linux-tp21593651p21598842.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: hibernate3-maven-plugin Error
Jean-Philippe Steinmetz-3 wrote: > > The odd thing about this is that I have a persistence.xml at the path > src/main/java/META-INF/persistence.xml. I guess you should place it in src/main/resources/META-INF/persistence.xml -- View this message in context: http://www.nabble.com/hibernate3-maven-plugin-Error-tp21579183p21598817.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: Can the maven-upload-plugin be used in a open source project?
David, Tim and Dan - extremely sorry about this delayed reply. I actually read these replies immediately when you posted but since it was too late in the night, i just rushed home with replying and forgot about this until today :) David and Tim, thanks for explaining the licenses to me - that helped. Dan, thanks for pointing me to the moved plugin. I will give it a try. -- View this message in context: http://www.nabble.com/Can-the-maven-upload-plugin-be-used-in-a-open-source-project--tp21543256p21598800.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
Can the maven-upload-plugin be used in a open source project?
I was working on a Maven project and was looking for a plugin which could upload some documentation to some remote location. While searching this mailing list i came across the maven-upload-plugin which is hosted at http://repository.atlassian.com/maven2/com/atlassian/maven/plugins/maven-upload-plugin/1.1/ http://repository.atlassian.com/maven2/com/atlassian/maven/plugins/maven-upload-plugin/1.1/ Its exactly what i was looking for. But is that plugin meant to be used in a open source project? I am curious since the plugin is hosted at a *.com domain. Any inputs? -- View this message in context: http://www.nabble.com/Can-the-maven-upload-plugin-be-used-in-a-open-source-project--tp21543256p21543256.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: maven-ear-plugin: Always throws "Embedded error: Unknown artifact type[test-jar]"
First of all, thank you for your inputs snicoll. snicoll wrote: > > The modules configuration is completely useless since the EAR plugin will > build the modules list using the dependencies section of your EAR project. > You are right :) I realized that, just a few minutes before you posted, after following these test cases in SVN http://svn.apache.org/viewvc/maven/plugins/trunk/maven-ear-plugin/src/test/resources/projects/ snicoll wrote: > > You have a test-jar without a scope test so the ear plugin tries to > package > it since it's not scoped properly. > Right, that's what seems to be happening. Here's a trimmed down version of the pom.xml which manifests the issue: org.myapp sample-maven-ear-app 0.1.0-SNAPSHOT ear Sample Maven EAR org.someapp.ejb someejbapp 1.0.0 ejb All i am trying to do is package "only" the someejbapp.jar into the EAR. I do not want the rest of the nested dependency to be packaged in the EAR. This nested dependency has the test-jar and i have no control over changing the scope of that test-jar. I have been searching the EAR plugin docs and haven't yet found a way to include only the someejbapp.jar in the EAR. Is it possible? Did i miss some existing documentation? -- View this message in context: http://www.nabble.com/maven-ear-plugin%3A-Always-throws-%22Embedded-error%3A-Unknown-artifact-type-test-jar-%22-tp21370128p21435283.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: Cannot compile simple code
What does the following command output: mvn -version especially the Java version -- View this message in context: http://www.nabble.com/Cannot-compile-simple-code-tp21412538p21412753.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: required artifact is missing ......
To add to what Wendy posted; the screenshot shows that the artifact is under D:\Daten\maven2-local\. Is that your Maven repository? Have you configured Maven to use this as the repository (through settings.xml)? By default Maven uses the user's home directory as the repository. thomas2004 wrote: > > Here is the screen-shot of my repository. Can you see what is wrong? > > http://www.nabble.com/file/p21373356/pom.jpg > > > -- View this message in context: http://www.nabble.com/required-artifact-is-missing-..-tp21372605p21410613.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: required artifact is missing ......
Its' missing this one : local.sun.java.net:jaxws-ri:pom:2.1-EA3-SNAPSHOT thomas2004 wrote: > > [14:36:57]: Missing: > [14:36:57]: -- > [14:36:57]: 1) local.sun.java.net:jaxws-ri:pom:2.1-EA3-SNAPSHOT > -- View this message in context: http://www.nabble.com/required-artifact-is-missing-..-tp21372605p21372814.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
maven-ear-plugin: Always throws "Embedded error: Unknown artifact type[test-jar]"
I am using Maven-2.0.9 in a multi-module project. One of the modules uses the maven-ear-plugin to generate an ear. Here's how it looks like: Parent pom.xml: - 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";> ParentArtifact 0.1.0-SNAPSHOT pom myjarOne myjarTwo enterprise_Ear Module1 = Jar artifact: - 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";> ParentArtifact myjarOne 0.1.0-SNAPSHOT jar Module 2 = Jar artifact: - 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";> ParentArtifact myjarTwo 0.1.0-SNAPSHOT jar Module 3 = Ear artifact: - 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";> ParentArtifact enterprise_Ear ear org.apache.maven.plugins maven-ear-plugin blah.blah myjarOne blah.blah myjarTwo blah.blah myjarTwo someversion jar blah.blah myjarOne someversion jar When i run mvn clean package on the parent pom, i always get a [INFO] [ear:generate-application-xml] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to initialize ear modules Embedded error: Unknown artifact type[test-jar] This happens irrespective of whether i include any "modules" in the ear plugin configuration. No matter what i tried, i keep getting this error. I then decided to run mvn in debug mode and this is what i see in the logs: [DEBUG] Resolving ear modules ... [DEBUG] Resolving ear module[jar:blah.blah.blah:myjarOne] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to initialize ear modules Embedded error: Unknown artifact type[test-jar] [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to initialize ear modules at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to initialize ear modules at org.apache.maven.plugin.ear.AbstractEarMojo.execute(Abst
Re: Plugin execution order incorrect in Maven-2.0.9 when multiple plugins are associated with the same phase
Jörg Schaible-2 wrote: > > Basically I mean the possibility to turn a POM in some kind of Ant build > script. Especially I refer the 3rd paragraph here: > http://maven.apache.org/background/philosophy-of-maven.html. > ... > Meanwhile I can also see here on the Maven list some kind of "we must > support any cornercase" attitude, simply because some people do not want > to > follow Maven's best practices building their projects > Jörg, i understand what you are saying. The only reason i ventured this path, was because of the documentation which illustrated this kind of ability with plugins. Again, i am not blaming anyone and i do understand that the usecase i am trying is not something Maven supports. Fair enough :-) -- View this message in context: http://www.nabble.com/Plugin-execution-order-incorrect-in-Maven-2.0.9-when-multiple-plugins-are-associated-with-the-same-phase-tp21113516p21156079.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: Access Is Denied Error
ufuk dogdu wrote: > > C:\Documents and > Settings\udogdu.TRIDC-NT\logicaldoc-3.6-src\logicaldoc-util\target\classes > (access is denied) Does the user account through which the maven build is run, have write permissions to this folder? -- View this message in context: http://www.nabble.com/Access-Is-Denied-Error-tp21155999p21156030.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how to make surefire die if a single test fails
novotny wrote: > > > Hi, > > What maven configuration do I need to do to make maven die > completely if any test fails? > > Thanks, Jason > > As far as i know, that's the default behaviour. Unless you have set the maven.test.failure.ignore to true -- View this message in context: http://www.nabble.com/how-to-make-surefire-die-if-a-single-test-fails-tp21152426p21156002.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: Plugin execution order incorrect in Maven-2.0.9 when multiple plugins are associated with the same phase
Jörg Schaible-2 wrote: > > Well, personally I hope it will not change. Otherwise we will face a lot > more Ant-like POMs which contradicts IMHO the original design goal. > > - Jörg > I did not get this. Do you mean allowing the same plugin to be included multiple times for the same phase won't be a good feature? -- View this message in context: http://www.nabble.com/Plugin-execution-order-incorrect-in-Maven-2.0.9-when-multiple-plugins-are-associated-with-the-same-phase-tp21113516p21143702.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: maven always downloading pom files
alon2 wrote: > > why maven downloads the same poms over and over again-they aresuppouse to > be in my repository after the first time no? > > Alon, Please post the Maven logs/messages that you see. Also have you enabled snapshot repositories and does your pom depend on any SNAPSHOT version? -- View this message in context: http://www.nabble.com/maven-always-downloading-pom-files-tp21142628p21143388.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: Plugin execution order incorrect in Maven-2.0.9 when multiple plugins are associated with the same phase
brettporter wrote: > > This is a limitation of the way Maven currently specifies the > executions. While it might be changed in the future it is currently by > design. > I understand. Do you want me to raise a feature request? brettporter wrote: > > You seem to be using the "install" phase for a purpose it was not > designed for > I have to agree with that. But just for the benefit of others who are reading this - the limitation is not just with the install phase. brettporter wrote: > > I suggest moving these to a different location, using > standalone goals, or writing a custom mojo to perform the tasks in > sequence (Don's mojo-executor plugin can help). > Thanks Brett, i will have a look. -- View this message in context: http://www.nabble.com/Plugin-execution-order-incorrect-in-Maven-2.0.9-when-multiple-plugins-are-associated-with-the-same-phase-tp21113516p21141720.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: Plugin execution order incorrect in Maven-2.0.9 when multiple plugins are associated with the same phase
Merging the executions of the plugin, atleast in this case, is not possible. Merging will make it: ABCArtifact Step1 deploy install Step3 undeploy install So there will be no room for Step2 (which comes from a different plugin). This was the original reason why i am repeating the same plugin multiple times. John Stoneham wrote: > > On Mon, Dec 22, 2008 at 4:10 AM, Stephen Connolly > wrote: >> AFAIK, You cannot repeat the same plugin multiple times in the plugins >> section. >> >> That is not to say that Maven should not support what you are trying to >> do, >> just that my understanding of the rules of Maven for 2.0.x are that you >> cannot do what you are trying to do using only one phase. > > Yes. You'd need to merge the executions section instead. > > > - John > -- View this message in context: http://www.nabble.com/Plugin-execution-order-incorrect-in-Maven-2.0.9-when-multiple-plugins-are-associated-with-the-same-phase-tp21113516p21129073.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: Plugin execution order incorrect in Maven-2.0.9 when multiple plugins are associated with the same phase
Thanks to Brett Porter, i found that this is similar to an already reported issue http://jira.codehaus.org/browse/MNG-3719 I'll create a simple reproducible application and attach to that issue with more details. In the meantime, let me see if can i find a workaround for this issue. -- View this message in context: http://www.nabble.com/Plugin-execution-order-incorrect-in-Maven-2.0.9-when-multiple-plugins-are-associated-with-the-same-phase-tp21113516p21123663.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: Plugin execution order incorrect in Maven-2.0.9 when multiple plugins are associated with the same phase
No matter what i try, the ordering is not working. Let me know if i have to
report a JIRA with a sample application attached.
Jaikiran wrote:
>
> I am seeing an issue with the order in which the plugin execution happens
> when there are multiple plugin associated with the same phase. I am using
> Maven 2.0.9. As per the documentation, the order in which they should be
> executed is the same as the order in which they are being defined in the
> POM. However, i don't see this happening. Here's my (sample) POM:
>
>
>
>
>
>
>
> something.something.ABC
> ABCArtifact
> ${someversionofABC}
>
>
>
>
>
>
> Step1
>
> deploy
>
> install
>
>
>
>
>
>
>
>
>
>
> maven-antrun-plugin
>
>
> Step2
> install
>
> run
>
> ... // other stuff
>
>
>
>
>
>
>
> something.something.ABC
> ABCArtifact
> ${someversionofABC}
>
>
>
> Step3
>
> undeploy
>
> install
> ... // other stuff
>
>
>
>
>
>
> As can be seen, the POM has 3 steps: Step1 Step2 and Step3 all bound to
> the "install" phase. Step1 and Step3 use plugin ABC where as Step2 uses
> plugin XYZ. Based on the POM ordering and the Maven documentation, the
> order of execution is expected to be Step1 then Step2 and then Step3.
> However i am consistently seeing the following incorrect order Step3 then
> Step1 and then Step2.
>
> Am i missing something?
>
--
View this message in context:
http://www.nabble.com/Plugin-execution-order-incorrect-in-Maven-2.0.9-when-multiple-plugins-are-associated-with-the-same-phase-tp21113516p21123472.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: Cleaning local repository
Maybe this might help http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html It has a excludes attribute where you can pass the 3rd party groupId:artifactId Pavel Bernshtam wrote: > > For Continuous Integration build I need to build all my projects for > sources, so I need somehow remove all "my" artifacts from the local > repository before the build (but leave there 3rd party artifacts). > Is there any maven plugin or tool for it or I just need to run some > script before the build which will clean the local repository > selectively? > > Thank you > > > > Pavel > > > -- View this message in context: http://www.nabble.com/Cleaning-local-repository-tp21114004p21114145.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: [Newbie] Maven can't find javac
What does your pom.xml look like? Try adding the compiler plugin to your pom
with the following configuration:
maven-compiler-plugin
${JAVA_HOME}/bin/javac
...
--
View this message in context:
http://www.nabble.com/-Newbie--Maven-can%27t-find-javac-tp21113688p21113760.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
Plugin execution order incorrect in Maven-2.0.9 when multiple plugins are associated with the same phase
I am seeing an issue with the order in which the plugin execution happens
when there are multiple plugin associated with the same phase. I am using
Maven 2.0.9. As per the documentation, the order in which they should be
executed is the same as the order in which they are being defined in the
POM. However, i don't see this happening. Here's my (sample) POM:
something.something.ABC
ABCArtifact
${someversionofABC}
Step1
deploy
install
maven-antrun-plugin
Step2
install
run
... // other stuff
something.something.ABC
ABCArtifact
${someversionofABC}
Step3
undeploy
install
... // other stuff
As can be seen, the POM has 3 steps: Step1 Step2 and Step3 all bound to the
"install" phase. Step1 and Step3 use plugin ABC where as Step2 uses plugin
XYZ. Based on the POM ordering and the Maven documentation, the order of
execution is expected to be Step1 then Step2 and then Step3. However i am
consistently seeing the following incorrect order Step3 then Step1 and then
Step2.
Am i missing something?
--
View this message in context:
http://www.nabble.com/Plugin-execution-order-incorrect-in-Maven-2.0.9-when-multiple-plugins-are-associated-with-the-same-phase-tp21113516p21113516.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: Does requireProperty consider system environment variables?
Great, the intermediate property trick works!
Here's what i did:
${JAVA_HOME}
Then in the enforcer plugin:
java.home
"Please set JAVA_HOME"
Thanks for the help :)
Jaikiran wrote:
>
> Matthew,
>
> That's a good idea :)
>
> Let me give it a try and see how it behaves. Will post the outcome.
>
>
--
View this message in context:
http://www.nabble.com/Does-requireProperty-consider-system-environment-variables--tp20936086p20950262.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Does requireProperty consider system environment variables?
Matthew,
That's a good idea :)
I had thought about it once, but then i guessed that if the JAVA_HOME is not
set, then the intermediate property would be set to the literal
${env.JAVA_HOME} by the following:
${env.JAVA_HOME}
Let me give it a try and see how it behaves. Will post the outcome.
Matthew Jaskula wrote:
>
> I would have thought that 'env.JAVA_HOME' would have worked, but it
> appears
> that it does not.
>
> If you don't want to write a rule, it looks like you can workaround with
> an
> intermediate property. Just set a property to the value of the environment
> variable and enforce that property. A tiny bit more confusing, but it's
> less
> code, and less to change when support for this is added to the plugin.
>
> Example:
>
> ..
>
> ${env.JAVA_HOME}
>
> ..
>
> org.apache.maven.plugins
> maven-enforcer-plugin
>
>
> enforce-property
>
> enforce
>
>
>
>
> javaHome
>
>
> true
>
>
>
>
> ..
>
> --
> Matthew Jaskula
> [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Does-requireProperty-consider-system-environment-variables--tp20936086p20949993.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Does requireProperty consider system environment variables?
Thanks, That answers my question :-) Stephen Connolly-2 wrote: > > Write a custom enforcer rule! > > -- View this message in context: http://www.nabble.com/Does-requireProperty-consider-system-environment-variables--tp20936086p20936504.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Does requireProperty consider system environment variables?
I am using Maven-2.0.9 and the enforcer plugin within my pom http://maven.apache.org/plugins/maven-enforcer-plugin/rules/index.html http://maven.apache.org/plugins/maven-enforcer-plugin/rules/index.html Within this plugin i am using the requireProperty rule to ensure that a environment property is set by the user before running mvn http://maven.apache.org/plugins/maven-enforcer-plugin/rules/requireProperty.html http://maven.apache.org/plugins/maven-enforcer-plugin/rules/requireProperty.html Here's the pom: org.apache.maven.plugins maven-enforcer-plugin enforce-property enforce JAVA_HOME "Please set JAVA_HOME" true This rule always fails even if the user has set the JAVA_HOME from the command prompt: export JAVA_HOME=/home/me/Java Does this rule, consider the system level environment variables? I could test the enforcer rule successfully against a property that was set within the pom. Is there any other way i can enforce the JAVA_HOME to be set? -- View this message in context: http://www.nabble.com/Does-requireProperty-consider-system-environment-variables--tp20936086p20936086.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven lifecycle - Is there a "run-only-once-in-a-lifetime" phase?
Thanks Wendy, i'll give that a try. Wendy Smoak-3 wrote: > > > Try false... > > http://maven.apache.org/ref/2.0.9/maven-model/maven.html#class_plugin > > -- > Wendy > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Maven-lifecycle---Is-there-a-%22run-only-once-in-a-lifetime%22-phase--tp20913469p20935964.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven lifecycle - Is there a "run-only-once-in-a-lifetime" phase?
I am using Maven-2.0.9. In my project, i have a parent pom and n child poms. Something like this: Parent POM: child-one child-two maven-antrun-plugin doSomething install run Note the "execution" which will be run during install phase of each module (child-one, child-two etc...). I am looking for a phase which will be run only once during the lifetime of the maven build process. Or is there some way i can make the plugin run only once during the build, even if the child modules inherit them? -- View this message in context: http://www.nabble.com/Maven-lifecycle---Is-there-a-%22run-only-once-in-a-lifetime%22-phase--tp20913469p20913469.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to add a local jar to the classpath of exec-maven-plugin
Stephen Connolly-2 wrote: > > Options: > > 1. Add xyz to your repo (seriously, this is the easiest) > > 2. Add xyz as a dependency to the plugin using the system scope (not too > difficult, but you'd be better off with 1 as once you start using the > system > scope, you'll incorrectly think it's the solution to all your problems and > then it will bite you in the ass somewhere else) > Thanks for the ideas and the quick reply, Stephen. I'll add the xyz to the repo - looks like an elegant approach. Thanks! -- View this message in context: http://www.nabble.com/How-to-add-a-local-jar-to-the-classpath-of-exec-maven-plugin-tp20893674p20894581.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to add a local jar to the classpath of exec-maven-plugin
I am using Maven2 and trying to run a java class from Maven using the exec-maven-plugin. Here's how it looks like: org.codehaus.mojo exec-maven-plugin 1.1-beta-1 exec java -classpath org.myapp.client.Client Notice the use of . The org.myapp.client.Client class also has a dependency on a local jar file xyz.jar (which is not in maven repo). I have the path to the jar file, but is there any way i can pass this to the classpath of the exec-maven-plugin? -- View this message in context: http://www.nabble.com/How-to-add-a-local-jar-to-the-classpath-of-exec-maven-plugin-tp20893674p20893674.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
