Re: [maven-failsafe-plugin] Failsafe+Jetty integration test trigger surefire twice
Hi Stephen, I like your second post ;) One the other hand it probably means that you already know that pestering jetty plugin people won't help! still, it's frustrating to see some phase triggered more than what is needed. I guess i have better things to do than trying to perfect something already working cheers -- View this message in context: http://n2.nabble.com/maven-failsafe-plugin-Failsafe-Jetty-integration-test-trigger-surefire-twice-tp4666895p4672838.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: Always download dependencies with classifier
Did you try any of the latest recommended versions of Maven, like 2.2.1? Maven 2.1.0 is generally a version to stay away from as it has issues... /Anders On Thu, Mar 4, 2010 at 07:03, Thunder Farmer wrote: > Hi, > > Thanks for your quick response. > Here I provide more information. > I can reproduce the issue by creating a simple project and adding a > dependency with classifier to it. > I create the project by "mvn archetype:create" command. > In the pom, I add a dependency: > > > com.informix > ifxjdbc 3.50 > JC3 > compile > > The informix JDBC jar and it's pom file are already in our local repo, and > I have local repo in my setting.xml > > Every time when I run "mvn compile", I get below output in the console > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > Downloading: > http://repo1.maven.org/maven2/com/informix/ifxjdbc/3.50/ifxjdbc-3.50.pom > [INFO] [compiler:compile] > > Seems it always tries to download the artifact. > Though it doesn't really download the jar file, it consume significant time > to connect remote repo for a large project. > > Is it expected behavior of Maven? > > The project is attached. > > Thanks, > Thunder > > > > On Thu, Mar 4, 2010 at 10:51 AM, Wendy Smoak wrote: > >> On Wed, Mar 3, 2010 at 9:44 PM, Thunder Farmer >> wrote: >> > My problems is that seems Maven always download dependencies with >> classifier >> > even I specify the version. >> > Is it the expected behavior or some thing goes wrong? >> > >> > Maven version: 2.1.0-M1 >> > Java version: 1.5.0_06 >> >> This is the right place, but we need more information. Can you post a >> snippet of the build output or error message that you're seeing, and >> maybe the relevant portion of your pom.xml file (the problematic >> )? >> >> You might also try the build with the latest recommended stable Maven >> version from http://maven.apache.org/download.html and see if it's >> still a problem. >> >> -- >> Wendy >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > > -- > Listen to Your Heart > Follow Your Heart > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
Re: Always download dependencies with classifier
On Wed, Mar 3, 2010 at 9:44 PM, Thunder Farmer wrote: > My problems is that seems Maven always download dependencies with classifier > even I specify the version. > Is it the expected behavior or some thing goes wrong? > > Maven version: 2.1.0-M1 > Java version: 1.5.0_06 This is the right place, but we need more information. Can you post a snippet of the build output or error message that you're seeing, and maybe the relevant portion of your pom.xml file (the problematic )? You might also try the build with the latest recommended stable Maven version from http://maven.apache.org/download.html and see if it's still a problem. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Always download dependencies with classifier
Hello All, My problems is that seems Maven always download dependencies with classifier even I specify the version. Is it the expected behavior or some thing goes wrong? Maven version: 2.1.0-M1 Java version: 1.5.0_06 This is first time I ask question on Maven user list. If this is NOT the right way, pls help correct me. Thanks, Thunder
Re: Newbie Maven layout question
user09772 wrote: How can a module be independent? meaning standalone within eclipse. because as it is now, the parent pom is responsible to glue everything together at build time (not the webapp module for example within eclipse). The Eclipse project Module 4 will have a POM that creates a jar file with a groupid, an artifactId and a version. If you are smart you will have a Nexus repository where the POM will deploy module4.jar The Eclipse project Module2 will have a POM that has a dependency on the module4 jar identifying it with the correct groupid, the artifactId and the version. it will deploy the module2.jar in the repository The Eclipse project Module 3 will have a POM that creates a jar file with a groupid, an artifactId and a version. and deploy the module3.jar in the repository The Eclipse project Module1 will have a POM that has a dependency on the module1, module 2 and module3 jars identifying each with the correct groupid, the artifactId and the version. It will create a WAR file (if that is what you want). It does not need to reference module 4 since module2's dependency on module 4 is known through the pom file in module2. Your life just got a lot simpler. Ron user09772 wrote: Thanks that is an excellent resource. I think parent poms is what i was looking for. The way i understand it parent poms are used to simply install the proper modules? so for each product its possible to have a parent pom which ties various modules into the repro. If module1 depends on module2 & module3, but module4 only needs to be visible to module2. How can i do this hierarchy with parent poms? Will the parent pom have all the modules, and module4 have module2 as it's dependency? Patrick Turcotte-3 wrote: Part of your problem could/(should?) be resolved with parent poms. A good read is the sonatype maven book ( http://www.sonatype.com/products/maven/documentation/book-defguide) Patrick On 10-03-02 02:18 PM, user09772 wrote: dahoffer wrote: Without knowing details all I can give are general suggestions... - Things you want to version/branch as a unit go in the same project (may have several modules). - Common things that are used in more than one project go in a separate project (may have several modules) and are depended on as needed. -Dave Thanks for the response. Right. so all the projects i mentioned would need to be versioning (the commands will change that the services use, the services will change that the rest projects use etc.). That is at a high level point of view right. I'm probably thinking more on how to use Maven modules to provide separation between each of the components. The main thing i would like to accomplish is have the ability to switch out any of the projects (modules?) with another one and build the system using those new modules. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Source for maven-jibx-plugin
On Wed, Mar 3, 2010 at 3:00 PM, marilysa wrote: > Does anyone know how to get the source code and license information for > maven-jibx-plugin? The web site gives a link to the license, but that link > is broken. It gives a link to the source code repository, but access to > that page is disabled. It gives instructions for using CVS to fetch the > source as an anonymous user, but the commands do not work. Several of us > here have tried to obtain the sources and license, with no success. It's still in the cvs. The code is browsable via http://jibx.cvs.sourceforge.net/viewvc/jibx/maven-jibx-plugin/ Cvs works, use the Sourceforge project developer page for access details: http://sourceforge.net/projects/jibx/develop > My company is using maven-jibx-plugin in building one of our products, and > we have strict requirements regarding use of Open Source IP. We are > required to have the sources stored in a central IP database, as well as the > complete text of the license. jibx is under BSD license. Storing the sources is not required for code under BSD-style licenses (take my word for it :) ) Kalle - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Source for maven-jibx-plugin
Hello, Maven users, Does anyone know how to get the source code and license information for maven-jibx-plugin? The web site gives a link to the license, but that link is broken. It gives a link to the source code repository, but access to that page is disabled. It gives instructions for using CVS to fetch the source as an anonymous user, but the commands do not work. Several of us here have tried to obtain the sources and license, with no success. My company is using maven-jibx-plugin in building one of our products, and we have strict requirements regarding use of Open Source IP. We are required to have the sources stored in a central IP database, as well as the complete text of the license. Any help or advice on getting the sources would be appreciated. Thanks, Marilyn Sander - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Working locally, building remotely?
Hi, How about : work on your computer (locally). commit code to versionning system on "remote" have automatic build system checkout new code, package and then deploy on maven repository (like nexus or artifactory). Patrick On 10-03-03 07:27 AM, Manos Batsis wrote: > > Hello, > > Sorry if this sounds dumb, but I was wondering what is the best way to > iteratively work on a multiproject locally, have it build remotely, > then deploy locally again. Any ideas welcome! > > Cheers, > > Manos > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Patrick Turcotte Développeur/Architecte Java patrick.turco...@revolutionlinux.com (819) 780-8955, poste 1129 Sans frais 1-800-996-8955, poste 1129 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANNOUNCEMENT] - Maven License Verifier Plugin 0.2-SNAPSHOT
Hi Laurent, first of all many thanks for taking the time My first question: Which release of Maven do you use ? laurent.perez wrote: > > Hello > > I've tried, but did not manage to produce a report, or to check the > licenses , I'm getting an NPE whenever I try to run it after "test", I > get no results if I try "mvn clean licence-verifier:report". > The documentation is a little bit lacking ;) That's of course a point i have to enhance the documentation about that... Can you help me ? Thanks I hope..;-)... Would you try to bind the plugin to a particular phase and just do a mvn test (and take a look if some output has been produced). test check This is just to isolate the problem. Many thanks I've already filed a bug into my issue tracking system... Kind regards Karl Heinz Marbaise -- View this message in context: http://old.nabble.com/-ANNOUNCEMENTMaven-License-Verifier-Plugin-0.2-SNAPSHOT-tp27658754p27772725.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
Why does maven-resources-plugin:copy-resources not filter?
I've configured maven-resources-plugin with two executions to apply
separate filters, but the output is not filtered! The debug log says
it found the property in the filter file...and it says it found the
file to apply the filter to. Why is it not filtered?
org.apache.maven.plugins
maven-resources-plugin
win-copy-resources
process-resources
copy-resources
${project.build.directory}/win-cp.properties
${project.build.directory}/extra-resources
src/main/resources
true
win-app.properties
unix-copy-resources
process-resources
copy-resources
${project.build.directory}/unix-cp.properties
${project.build.directory}/extra-resources
src/main/resources
true
unix-app.properties
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Newbie Maven layout question
How can a module be independent? meaning standalone within eclipse. because as it is now, the parent pom is responsible to glue everything together at build time (not the webapp module for example within eclipse). user09772 wrote: > > Thanks that is an excellent resource. > > I think parent poms is what i was looking for. > > The way i understand it parent poms are used to simply install the proper > modules? so for each product its possible to have a parent pom which ties > various modules into the repro. > > If module1 depends on module2 & module3, but module4 only needs to be > visible to module2. How can i do this hierarchy with parent poms? Will > the parent pom have all the modules, and module4 have module2 as it's > dependency? > > > Patrick Turcotte-3 wrote: >> >> >> Part of your problem could/(should?) be resolved with parent poms. >> >> A good read is the sonatype maven book ( >> http://www.sonatype.com/products/maven/documentation/book-defguide) >> >> Patrick >> >> On 10-03-02 02:18 PM, user09772 wrote: >>> >>> >>> dahoffer wrote: >>> Without knowing details all I can give are general suggestions... - Things you want to version/branch as a unit go in the same project (may have several modules). - Common things that are used in more than one project go in a separate project (may have several modules) and are depended on as needed. -Dave >>> Thanks for the response. >>> >>> Right. so all the projects i mentioned would need to be versioning (the >>> commands will change that the services use, the services will change >>> that >>> the rest projects use etc.). That is at a high level point of view >>> right. >>> I'm probably thinking more on how to use Maven modules to provide >>> separation >>> between each of the components. >>> >>> The main thing i would like to accomplish is have the ability to switch >>> out >>> any of the projects (modules?) with another one and build the system >>> using >>> those new modules. >>> >> >> > > -- View this message in context: http://old.nabble.com/Newbie-Maven-layout-question-tp27759332p27772511.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 layout question
Thanks that is an excellent resource. I think parent poms is what i was looking for. The way i understand it parent poms are used to simply install the proper modules? so for each product its possible to have a parent pom which ties various modules into the repro. If module1 depends on module2 & module3, but module4 only needs to be visible to module2. How can i do this hierarchy with parent poms? Will the parent pom have all the modules, and module4 have module2 as it's dependency? Patrick Turcotte-3 wrote: > > > Part of your problem could/(should?) be resolved with parent poms. > > A good read is the sonatype maven book ( > http://www.sonatype.com/products/maven/documentation/book-defguide) > > Patrick > > On 10-03-02 02:18 PM, user09772 wrote: >> >> >> dahoffer wrote: >> >>> Without knowing details all I can give are general suggestions... >>> >>> - Things you want to version/branch as a unit go in the same project >>> (may have several modules). >>> - Common things that are used in more than one project go in a >>> separate project (may have several modules) and are depended on as >>> needed. >>> >>> -Dave >>> >>> >>> >>> >> Thanks for the response. >> >> Right. so all the projects i mentioned would need to be versioning (the >> commands will change that the services use, the services will change that >> the rest projects use etc.). That is at a high level point of view >> right. >> I'm probably thinking more on how to use Maven modules to provide >> separation >> between each of the components. >> >> The main thing i would like to accomplish is have the ability to switch >> out >> any of the projects (modules?) with another one and build the system >> using >> those new modules. >> > > -- View this message in context: http://old.nabble.com/Newbie-Maven-layout-question-tp27759332p27771944.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-dependency-plugin:build-classpath bug
Yeah, but not everything is Java on Windows. You can't pass that to the Windows API, for instance. In my case I would be at the mercy how InstallAnywhere deals with this. If it just reads the file verbatim and passes it on to Windows it isn't going to work. -Dave On Wed, Mar 3, 2010 at 10:38 AM, Wayne Fay wrote: >> Will create something like classpath=packages\foo.jar instead of >> classpath=packages\\foo.jar so it can't be read. Is there a fix for > > I'd think the fix should be to make all the \'s into /'s which Java on > Windows seems to deal with just fine... > > Wayne > > - > 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: [ANNOUNCEMENT] - Maven License Verifier Plugin 0.2-SNAPSHOT
Hello
I've tried, but did not manage to produce a report, or to check the
licenses , I'm getting an NPE whenever I try to run it after "test", I
get no results if I try "mvn clean licence-verifier:report".
The documentation is a little bit lacking ;)
Can you help me ? Thanks
My configuration :
-
com.soebes.maven.plugins.mlv
maven-license-verifier-plugin
0.2-SNAPSHOT
true
Output of : mvn test license:report : NPE
-
[INFO] [license-verifier:report {execution: default-cli}]
[INFO] LicenseVerifierReport:execute()
[INFO] LicenseVerifierReport:generate()
[INFO] Loading
/home/laurent/Desktop/SVN/4.0.x//src/main/licenses/licenses.xml
licenses file.
[ERROR]
java.lang.NullPointerException
at
com.soebes.maven.plugins.mlv.licenses.LicenseValidator.getWarning(LicenseValidator.java:65)
at
com.soebes.maven.plugins.mlv.licenses.LicenseValidator.isWarning(LicenseValidator.java:382)
at
com.soebes.maven.plugins.mlv.licenses.LicenseValidator.isWarning(LicenseValidator.java:281)
at
com.soebes.maven.plugins.mlv.LicenseVerifierReport.doGenerateItemReport(LicenseVerifierReport.java:238)
at
com.soebes.maven.plugins.mlv.LicenseVerifierReport.doGenerateReport(LicenseVerifierReport.java:180)
at
com.soebes.maven.plugins.mlv.LicenseVerifierReport.generate(LicenseVerifierReport.java:482)
at
com.soebes.maven.plugins.mlv.LicenseVerifierReport.execute(LicenseVerifierReport.java:516)
Output of : mvn clean license:report : nothing is generated in target/site/
--
[INFO] [license-verifier:report {execution: default-cli}]
[INFO] LicenseVerifierReport:execute()
[INFO] LicenseVerifierReport:generate()
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
My src/main/licenses/license.xml :
--
Apache Software License 2.0
Apache Software License 2.0
Apache 2
Apache Software License 2.0
Apache Software License, Version 2.0
http://www.apache.org/licenses/LICENSE-2.0
http://www.apache.org/licenses/LICENSE-2.0.html
http://www.apache.org/licenses/LICENSE-2.0.txt
http://apache.org/licenses/LICENSE-2.0
http://apache.org/licenses/LICENSE-2.0.html
http://apache.org/licenses/LICENSE-2.0.txt
laurent
2010/2/19 Karl Heinz Marbaise :
>
> Hi to all,
>
> i'm happy to announce that the first SNAPSHOT release is available of the
> Maven License Verifier Plugin.
>
> The Release 0.2-SNAPSHOT contains only basic functionality and is not
> intended for production usage.
>
> The intention is to check if everything is correctly configured on my site
> that it will work with other setup's as well and the basics are working.
>
> If you are willing to give it a try i appreciate feedback in any
> form...concerning the functionality or the documentation or enhancements
> etc.
>
> The plugin is available from the following SNAPSHOT Repository:
>
> http://oss.sonatype.org/content/repositories/snapshots/
>
> The coordinates (GAV) are:
>
>
> com.soebes.maven.plugins.mlv
> maven-license-verifier-plugin
> 0.2-SNAPSHOT
>
>
> The current state of the documentation is located at:
>
> http://site.supose.org/maven-licenses-verifier-plugin/
>
> If you have any problems concerning the plugin give a mail on the list (or
> direct to me) or via issue tracker:
>
> http://www.supose.org/projects/show/mlv
>
> Kind regards
> Karl Heinz Marbaise
> Karl Heinz Marbaise
>
> --
> View this message in context:
> http://old.nabble.com/-ANNOUNCEMENTMaven-License-Verifier-Plugin-0.2-SNAPSHOT-tp27658754p27658754.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
>
>
--
http://blog.jdeuxe.info/";>http://blog.jdeuxe.info/ - Java
entreprise tips & tricks
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-dependency-plugin:build-classpath bug
> Will create something like classpath=packages\foo.jar instead of > classpath=packages\\foo.jar so it can't be read. Is there a fix for I'd think the fix should be to make all the \'s into /'s which Java on Windows seems to deal with just fine... Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Working locally, building remotely?
> Sorry if this sounds dumb, but I was wondering what is the best way to > iteratively work on a multiproject locally, have it build remotely, then > deploy locally again. Any ideas welcome! First, define local and remote. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: migrate an ant project to maven
> these variants contain source code, that could be new or replacement for > the source code in core modules. How can i build that kind of project? If New code should be ok, but replacement code should not be allowed in your codebase, this is just a bad practice that Ant allowed you to implement. In those cases, extract interfaces and use DI to inject the proper customer-specific implementation. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Reflexion about dependencies.
Hi Patrick For a more complete anwser, read: http://www.sonatype.com/people/2009/10/maven-tips-and-tricks-optimizing-with-the-maven-dependency-plugin/ Thank you for your input. Stéphane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: XML output of missing dependencies
Thanks Jörg, Thanks for that response. However my question still remains. How can I get Maven to report to me, in XML format the missing dependencies. I know Maven currently dumps them out to the log/console in text format. Is there a plugin out there that can capture that info in XML? I'm trying to avoid parsing that text output. Or can someone point me to the Maven classes that produce that output so that I can grab that info before it is pretty-ed up and printed to the console. Then I can write my own plugin to process that information. Thanks Jörg Schaible-2 wrote: > > Hi Pankaj, > > Pankaj Tandon wrote at Wednesday, 3. March 2010 14:32: > >> >> Hi, >> I'm looking for a way to determine what artifacts are NOT in my corporate >> repository (for a certain maven project) so that I can script their >> addition to the corporate repository. >> >> So I started looking at the maven-dependency-plugin and was happy to see >> a >> goal called analyze that takes in a config param called outputXML. So >> that >> sounded just what I needed. >> >> But then I started looking closer and it seems that although the >> documentation of outputXML specifies "Output the xml for the missing >> dependencies", looking at the code (of >> http://svn.apache.org/viewvc/maven/plugins/tags/maven-dependency- > plugin-2.1/src/main/java/org/apache/maven/plugin/dependency/AbstractAnalyzeMojo.java?view=markup >> AbstractAnalyzeMojo ), outputXML really outputs usedUndeclared >> dependencies > > they are nor declared in the current POM, therefore they are missing. > >> NOT missing dependencies. > > this does not make sense, because to analyse the dependencies, they have > to > be present. They *cannot* be missing in the repository. > >> I think there is a distinction drawn between declared (in the POM) and >> missing (from the accessible repos) and it seems that outputXML only >> dumps >> the used-but-undeclared-in-pom dependencies. > > Not for the plugin and its purpose here. > >> My question is: Is there a way to dump (in XML preferably) the >> dependencies that are missing from accessible repositories? Maybe using >> some other plugin? > > Every plugin, that requires dependency resolution from Maven, will cause > the > Maven core to download the missing stuff. *If* something is missing, Maven > will report those all and stop with an error. > > This might not be exactly what you're looking for though... > > - Jörg > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://old.nabble.com/XML-output-of-missing-dependencies-tp27768224p27770365.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
Developing maven plugin.Can I use 'expression' and 'default-value' in my config objects.
I can create configuration parameter for my plugin and annotate it with
/**
* The greeting to display.
*
* @parameter expression="${sayhi.greeting}" default-value="Hello
World!"
*/
private String greeting;
This is said here
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
But I have my objects as config parameters. Can I use 'expression' and
'default-value' for its fields?
--
View this message in context:
http://old.nabble.com/Developing-maven-plugin.Can-I-use-%27expression%27-and-%27default-value%27-in-my-config-objects.-tp27769924p27769924.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-dependency-plugin:build-classpath bug
maven-dependency-plugin:build-classpath creates invalid property file
on Windows platform.
org.apache.maven.plugins
maven-dependency-plugin
2.1
generate-sources
build-classpath
true
;
packages
true
${project.build.directory}/classpath.properties
Will create something like classpath=packages\foo.jar instead of
classpath=packages\\foo.jar so it can't be read. Is there a fix for
this?
-Dave
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Reflexion about dependencies.
For a more complete anwser, read: http://www.sonatype.com/people/2009/10/maven-tips-and-tricks-optimizing-with-the-maven-dependency-plugin/ Patrick On 10-03-02 01:06 PM, Patrick Turcotte wrote: > mvn dependency:tree > > should help you see nested dependencies. The codehaus maven eclipse > plugin can also help you visualize it. > > Patrick > > On 10-03-02 12:16 PM, Wayne Fay wrote: > >>> The fact is that some dependencies that I use, handles other dependencies >>> that I use too. My IDE is therefore unable to tell me that I forget to add a >>> dependency because of the transitivity. >>> >>> >> If a given module uses an artifact directly, it must be included as a >> dependency in its pom file, not as a transitive dep. >> >> If that doesn't answer your question, perhaps a concrete explanation >> of what you're describing would make things more clear. >> >> Wayne >> >> - >> 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 > > -- Patrick Turcotte Développeur/Architecte Java patrick.turco...@revolutionlinux.com (819) 780-8955, poste 1129 Sans frais 1-800-996-8955, poste 1129 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: XML output of missing dependencies
Hi Pankaj, Pankaj Tandon wrote at Wednesday, 3. March 2010 14:32: > > Hi, > I'm looking for a way to determine what artifacts are NOT in my corporate > repository (for a certain maven project) so that I can script their > addition to the corporate repository. > > So I started looking at the maven-dependency-plugin and was happy to see a > goal called analyze that takes in a config param called outputXML. So that > sounded just what I needed. > > But then I started looking closer and it seems that although the > documentation of outputXML specifies "Output the xml for the missing > dependencies", looking at the code (of > http://svn.apache.org/viewvc/maven/plugins/tags/maven-dependency- plugin-2.1/src/main/java/org/apache/maven/plugin/dependency/AbstractAnalyzeMojo.java?view=markup > AbstractAnalyzeMojo ), outputXML really outputs usedUndeclared > dependencies they are nor declared in the current POM, therefore they are missing. > NOT missing dependencies. this does not make sense, because to analyse the dependencies, they have to be present. They *cannot* be missing in the repository. > I think there is a distinction drawn between declared (in the POM) and > missing (from the accessible repos) and it seems that outputXML only dumps > the used-but-undeclared-in-pom dependencies. Not for the plugin and its purpose here. > My question is: Is there a way to dump (in XML preferably) the > dependencies that are missing from accessible repositories? Maybe using > some other plugin? Every plugin, that requires dependency resolution from Maven, will cause the Maven core to download the missing stuff. *If* something is missing, Maven will report those all and stop with an error. This might not be exactly what you're looking for though... - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
XML output of missing dependencies
Hi, I'm looking for a way to determine what artifacts are NOT in my corporate repository (for a certain maven project) so that I can script their addition to the corporate repository. So I started looking at the maven-dependency-plugin and was happy to see a goal called analyze that takes in a config param called outputXML. So that sounded just what I needed. But then I started looking closer and it seems that although the documentation of outputXML specifies "Output the xml for the missing dependencies", looking at the code (of http://svn.apache.org/viewvc/maven/plugins/tags/maven-dependency-plugin-2.1/src/main/java/org/apache/maven/plugin/dependency/AbstractAnalyzeMojo.java?view=markup AbstractAnalyzeMojo ), outputXML really outputs usedUndeclared dependencies NOT missing dependencies. I think there is a distinction drawn between declared (in the POM) and missing (from the accessible repos) and it seems that outputXML only dumps the used-but-undeclared-in-pom dependencies. My question is: Is there a way to dump (in XML preferably) the dependencies that are missing from accessible repositories? Maybe using some other plugin? Thanks in advance, all you mavenPeople! Pankaj -- View this message in context: http://old.nabble.com/XML-output-of-missing-dependencies-tp27768224p27768224.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: Reflexion about dependencies.
Stéphane TOUSSAINT wrote at Mittwoch, 3. März 2010 13:48: > >> http://jira.codehaus.org/browse/MNG-2589 and linked stuff. >> > Thanks Jörg this is the issue I have to keep an eye on. You can already simulate this though. Assuming you're already using a depMgmt section to define your versions, you may simply declare all artifacts also with scope runtime. That way you're forced to declare all deps for scope compile locally again. However, as Benjamin explained, there might be more than you expect. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Reflexion about dependencies.
http://jira.codehaus.org/browse/MNG-2589 and linked stuff. Thanks Jörg this is the issue I have to keep an eye on. Stéphane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: properties in assembly plugin
Thanks and sorry
it was easy ...
ste
On 03/03/2010 12.59, Andreas M wrote:
Stefano Nichele-2 wrote:
Hi All,
in my assembly file I have several fileSets sections and some of them
are used to copy some files under/lib , others/bin, others
in/licenses. My issue is the I'd like to have configured
just in one place and not replicated in all fileSets sections.
Is there a way to set in once in the assembly file or in the pom.xml as
configuration property ?
Thanks in advance
ste
Well, I reference ${project.build.directory} with no problems in my
assembly.xml, so you should just be able to define a property in your pom
and go with it.
Does that not work?
/Andreas
--
Stefano Nichele
Funambol Chief Architect
Funambol :: Open Source Mobile Cloud Sync and Push Email
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Working locally, building remotely?
Hello, Sorry if this sounds dumb, but I was wondering what is the best way to iteratively work on a multiproject locally, have it build remotely, then deploy locally again. Any ideas welcome! Cheers, Manos - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
migrate an ant project to maven
Hi Maven users, we have a project with ant build script that we want to migrate to maven. This project contains of "backend_core" and "frontend_core" modules, there are also variants for each customer. so "customer_backend" and "customer_frontend", these variants contain source code, that could be new or replacement for the source code in core modules. How can i build that kind of project? If i have a class twice in core and customer module, then i get compilation failure with duplicate class error. regards, Valerij
Re: properties in assembly plugin
Stefano Nichele-2 wrote:
>
> Hi All,
> in my assembly file I have several fileSets sections and some of them
> are used to copy some files under /lib , others /bin, others
> in /licenses. My issue is the I'd like to have configured
> just in one place and not replicated in all fileSets sections.
>
> Is there a way to set in once in the assembly file or in the pom.xml as
> configuration property ?
>
> Thanks in advance
> ste
>
Well, I reference ${project.build.directory} with no problems in my
assembly.xml, so you should just be able to define a property in your pom
and go with it.
Does that not work?
/Andreas
--
View this message in context:
http://old.nabble.com/properties-in-assembly-plugin-tp27767079p27767294.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
properties in assembly plugin
Hi All, in my assembly file I have several fileSets sections and some of them are used to copy some files under /lib , others /bin, others in /licenses. My issue is the I'd like to have configured just in one place and not replicated in all fileSets sections. Is there a way to set in once in the assembly file or in the pom.xml as configuration property ? Thanks in advance ste - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [maven-failsafe-plugin] Failsafe+Jetty integration test trigger surefire twice
In any case, running your unit tests (which should be fast) multiple times just makes sure that they really pass ;-) [and with my serious hat on, will be twice as likely to catch those unstable bits of code that sporadically cause your unit tests that fail at random] -Stephen On 3 March 2010 11:33, Stephen Connolly wrote: > The jetty plugin forks a lifecycle to generate the exploded web > application... perhaps you need top perster the jetty maven plugin > developers to give you a goal for running exploded without forking a > lifecycle > > > On 3 March 2010 11:29, nodje wrote: > >> >> I've been using the standard configuration described in >> http://maven.apache.org/plugins/maven-failsafe-plugin/usage.html to be >> able >> to execute integration tests. >> That is, jetty:run-exploded goal is link to pre-integration-test phase in >> order to have a container to run integration test against. >> >> It works well so far, but I'm noticing only now that the surefire:test >> phase >> is triggered twice during the verify goal execution. This is largely >> lengthening the process. >> >> AFAIU it really is the binding of the jetty:run-exploded goal to the >> pre-integration-phase that is creating this situation: the whole Maven >> lifecycle seems to be re-executed. >> If not bound, everything execute as expected, but integration tests fail >> of >> course, since there's no container to run against. >> >> Can someone with experience in configuring integration test share >> experience >> here? >> >> I do not understand why binding jetty goal to pre-integration-test phase >> makes it restart the whole lifecycke. >> >> Any resources helping to understand what's exactly going on when binding >> plugin goals to lifecycle phases welcome! >> >> cheers >> >> -- >> View this message in context: >> http://n2.nabble.com/maven-failsafe-plugin-Failsafe-Jetty-integration-test-trigger-surefire-twice-tp4666895p4666895.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-failsafe-plugin] Failsafe+Jetty integration test trigger surefire twice
The jetty plugin forks a lifecycle to generate the exploded web application... perhaps you need top perster the jetty maven plugin developers to give you a goal for running exploded without forking a lifecycle On 3 March 2010 11:29, nodje wrote: > > I've been using the standard configuration described in > http://maven.apache.org/plugins/maven-failsafe-plugin/usage.html to be > able > to execute integration tests. > That is, jetty:run-exploded goal is link to pre-integration-test phase in > order to have a container to run integration test against. > > It works well so far, but I'm noticing only now that the surefire:test > phase > is triggered twice during the verify goal execution. This is largely > lengthening the process. > > AFAIU it really is the binding of the jetty:run-exploded goal to the > pre-integration-phase that is creating this situation: the whole Maven > lifecycle seems to be re-executed. > If not bound, everything execute as expected, but integration tests fail of > course, since there's no container to run against. > > Can someone with experience in configuring integration test share > experience > here? > > I do not understand why binding jetty goal to pre-integration-test phase > makes it restart the whole lifecycke. > > Any resources helping to understand what's exactly going on when binding > plugin goals to lifecycle phases welcome! > > cheers > > -- > View this message in context: > http://n2.nabble.com/maven-failsafe-plugin-Failsafe-Jetty-integration-test-trigger-surefire-twice-tp4666895p4666895.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-failsafe-plugin] Failsafe+Jetty integration test trigger surefire twice
I've been using the standard configuration described in http://maven.apache.org/plugins/maven-failsafe-plugin/usage.html to be able to execute integration tests. That is, jetty:run-exploded goal is link to pre-integration-test phase in order to have a container to run integration test against. It works well so far, but I'm noticing only now that the surefire:test phase is triggered twice during the verify goal execution. This is largely lengthening the process. AFAIU it really is the binding of the jetty:run-exploded goal to the pre-integration-phase that is creating this situation: the whole Maven lifecycle seems to be re-executed. If not bound, everything execute as expected, but integration tests fail of course, since there's no container to run against. Can someone with experience in configuring integration test share experience here? I do not understand why binding jetty goal to pre-integration-test phase makes it restart the whole lifecycke. Any resources helping to understand what's exactly going on when binding plugin goals to lifecycle phases welcome! cheers -- View this message in context: http://n2.nabble.com/maven-failsafe-plugin-Failsafe-Jetty-integration-test-trigger-surefire-twice-tp4666895p4666895.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: Reflexion about dependencies.
Stéphane TOUSSAINT wrote at Mittwoch, 3. März 2010 10:59: > That is the point. > > A sample : > my.project:test:1.0-SNAPSHOT (a Project) > my.utility:xml:1.0 (an utils librarie) > dom4j:dom4j:1.6 (the well known XML library) > > I added to my.project:test the my.utility:xml which talk about XML which > use (and include in it's pom.xml) the dom4j:dom4j:1.6 artifact. > > my.project:test > |> my.utility:xml > |> dom4j:dom4j > > > I can now work with classes from my.utility:xml. Everything OK, > compiles, packages, as expected. > > But now, nothing prevents me to use directly classes from dom4j in my > own code. The compiler will not complains, but it should because the > dom4j is only a transitive dependency. I must add dom4j to > my.project:test pom.xml before using it, mustn't I ?. > This sample is light enough to take care of, but what if I play with a > lot more librairies. > > The point is why not treat dom4j:dom4j as a 'RUNTIME' library from the > my.project:test point of view ? The compiler will explicitly tell me > that dom4j classes are not part of my compilation classpath and that I > have to add it in my pom > > my.project:test > |> my.utility:xml > ||> dom4j:dom4j > |> dom4j:dom4j > > Hoping I make things more clear. http://jira.codehaus.org/browse/MNG-2589 and linked stuff. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Reflexion about dependencies.
That is the point. A sample : my.project:test:1.0-SNAPSHOT (a Project) my.utility:xml:1.0 (an utils librarie) dom4j:dom4j:1.6 (the well known XML library) I added to my.project:test the my.utility:xml which talk about XML which use (and include in it's pom.xml) the dom4j:dom4j:1.6 artifact. my.project:test |> my.utility:xml |> dom4j:dom4j I can now work with classes from my.utility:xml. Everything OK, compiles, packages, as expected. But now, nothing prevents me to use directly classes from dom4j in my own code. The compiler will not complains, but it should because the dom4j is only a transitive dependency. I must add dom4j to my.project:test pom.xml before using it, mustn't I ?. This sample is light enough to take care of, but what if I play with a lot more librairies. The point is why not treat dom4j:dom4j as a 'RUNTIME' library from the my.project:test point of view ? The compiler will explicitly tell me that dom4j classes are not part of my compilation classpath and that I have to add it in my pom my.project:test |> my.utility:xml | |> dom4j:dom4j |> dom4j:dom4j Hoping I make things more clear. Stéphane Wayne Fay a écrit : The fact is that some dependencies that I use, handles other dependencies that I use too. My IDE is therefore unable to tell me that I forget to add a dependency because of the transitivity. If a given module uses an artifact directly, it must be included as a dependency in its pom file, not as a transitive dep. If that doesn't answer your question, perhaps a concrete explanation of what you're describing would make things more clear. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Stéphane TOUSSAINT Tel : 01.61.08.50.27 Std : 01.61.08.50.20 Fax : 01.61.38.24.41
