buildnumber-maven-plugin
Hi,
I am trying to use buildnumber-maven-plugin with "install" goal. The plugin
seems to run with "package" only. Is there a way to make it run for
"install".
org.codehaus.mojo
buildnumber-maven-plugin
1.0-beta-4
validate
create
true
true
0
I am not able to get ${buildNumber} with "install" ?
TIA,
--
View this message in context:
http://old.nabble.com/buildnumber-maven-plugin-tp27559871p27559871.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: unit testing archetypes
in invoker.properties you will need to specify multiple executions, eg
invoker.goals.1=archetype:generate
invoker.goals.2=verify
the first one generates your project, the second builds it
Sent from my [rhymes with tryPod] ;-)
On 12 Feb 2010, at 01:43, Max Spring wrote:
This is exactly what I was looking for. Great!
One missing piece: If the instantiated archetype fails to build, I
want the integration test to fail.
So far a failure result is not getting propagated to the "outer"
Maven execution.
I assume this would need to be done as a postBuildHookScript?
Thank you!
-Max
On 2/11/2010 6:13 AM, Luke Patterson wrote:
On Wed, Feb 10, 2010 at 5:37 PM, Max Spring
wrote:
What would be a good approach to test an archetype project?
...
A minimal test would be to "instantiate" the archetype and to
build the resulting project.
Here's some cut-and-paste that I'm using:
org.apache.maven.plugins
maven-invoker-plugin
integration-test
install
run
${project.build.directory}/it/projectscloneProjectsTo>
org.apache.maven.plugins:maven-archetype-plugin:generategoal>
${project.build.directory}/it/repolocalRepositoryPath>
*
${basedir}/src/it/projects
${project.artifactId}
${project.groupId}
local
${project.version}
verify
false
true
then, your archetype will be run during integration-test phase for
all
subdirectories of, a test.properties file will
contain the inputs to the archetype:generate goal, and the verify
phase will be run on each newly generated project
to add a new test, add another directory under
with a test.properties file
--
e.g.
src/it/projects/firsttest/test.properties with contents:
groupId=com.foo
artifactId=firsttest
version=1.0.0
package=com.foo.firsttest
that will create a "firsttest" directory under
${project.build.directory}/it/projects/firsttest with the stuff
generated by your archetype, and then run the verify phase on the
newly generated "com.foo.firsttest" project
--
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn javadoc:fix doesn't understand custom source locations
Before I point you to docs about your question, I have to ask why you're using a custom source code location? Maven is about convention over configuration; you'll make your life (and everyone else that is part of your project) easier by following the Maven standards. /Anders On Fri, Feb 12, 2010 at 05:02, Rajesh Koilpillai < rajesh.koilpil...@gmail.com> wrote: > Hi, > > mvn javadoc:fix doesn't understand custom source locations. My source code > is available under c:\project\ejb\src\model. Any idea on how to add custom > directories, I couldn't locate this in the plug-in documentation though. > > [WARNING] > [WARNING] WARRANTY DISCLAIMER > [WARNING] > [WARNING] All warranties with regard to this Maven goal are disclaimed! > [WARNING] The changes will be done directly in the source code. > [WARNING] The Maven Team strongly recommends the use of a SCM software BEFO > RE executing this goal. > [WARNING] > [INFO] Are you sure to proceed? [Y]es [N]o > Y > [INFO] OK, let's proceed... > [WARNING] No previous artifact has been deployed, Clirr is ignored. > [WARNING] c:\project\ejb\src\main\java doesn't exist. Ignored it. > > > How do you add custom source locations? > > -- > Thanks, > - Rajesh Koilpillai >
mvn javadoc:fix doesn't understand custom source locations
Hi, mvn javadoc:fix doesn't understand custom source locations. My source code is available under c:\project\ejb\src\model. Any idea on how to add custom directories, I couldn't locate this in the plug-in documentation though. [WARNING] [WARNING] WARRANTY DISCLAIMER [WARNING] [WARNING] All warranties with regard to this Maven goal are disclaimed! [WARNING] The changes will be done directly in the source code. [WARNING] The Maven Team strongly recommends the use of a SCM software BEFO RE executing this goal. [WARNING] [INFO] Are you sure to proceed? [Y]es [N]o Y [INFO] OK, let's proceed... [WARNING] No previous artifact has been deployed, Clirr is ignored. [WARNING] c:\project\ejb\src\main\java doesn't exist. Ignored it. How do you add custom source locations? -- Thanks, - Rajesh Koilpillai
JAR with classifier being ignored
Maven version: 2.2.1 I am unable to figure out why the proper dependency is not being bundled into my project's WAR. My WAR module expresses a dependency on a SWF (a Flex thing) as follows com.sas.mis molly-swf 0.0.3 test swf I expect to see molly-swf-0.0.3-test.swf in my WAR. Instead I see molly-swf-0.0.3.swf. It is as if the test classifier is being ignored. What could be causing this problem? Sri -- View this message in context: http://old.nabble.com/JAR-with-classifier-being-ignored-tp27556754p27556754.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: unit testing archetypes
This is exactly what I was looking for. Great!
One missing piece: If the instantiated archetype fails to build, I want
the integration test to fail.
So far a failure result is not getting propagated to the "outer" Maven
execution.
I assume this would need to be done as a postBuildHookScript?
Thank you!
-Max
On 2/11/2010 6:13 AM, Luke Patterson wrote:
On Wed, Feb 10, 2010 at 5:37 PM, Max Spring wrote:
What would be a good approach to test an archetype project?
...
A minimal test would be to "instantiate" the archetype and to build the
resulting project.
Here's some cut-and-paste that I'm using:
org.apache.maven.plugins
maven-invoker-plugin
integration-test
install
run
${project.build.directory}/it/projects
org.apache.maven.plugins:maven-archetype-plugin:generate
${project.build.directory}/it/repo
*
${basedir}/src/it/projects
${project.artifactId}
${project.groupId}
local
${project.version}
verify
false
true
then, your archetype will be run during integration-test phase for all
subdirectories of, a test.properties file will
contain the inputs to the archetype:generate goal, and the verify
phase will be run on each newly generated project
to add a new test, add another directory under
with a test.properties file
--
e.g.
src/it/projects/firsttest/test.properties with contents:
groupId=com.foo
artifactId=firsttest
version=1.0.0
package=com.foo.firsttest
that will create a "firsttest" directory under
${project.build.directory}/it/projects/firsttest with the stuff
generated by your archetype, and then run the verify phase on the
newly generated "com.foo.firsttest" project
--
-
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
Can the site.xml inheritance be avoided ?
Hi Guys, I have a multi-module project and it just happens so that I want to have a totally seperate look & feel and menu-items in the site generated for just the parent. Hence I made my custom site.xml for that parent (reactor) module without reports and modules in the left menu. As for child modules, I want to have the maven's default look & feel and menu-items. But the problem is that now that I have introduced the site.xml for just the parent module, all my child modules are inheriting that structure, which I don't want, and instead have the maven's default site structure be used. Is there a way I can avoid inheriting the site.xml from the parent ?. Also, I would certainly want to avoid introducing site.xml file for each of the child module (20 to 25 in number) just to avoid this inheritance. Please comment. Thanks, Farhan. -- View this message in context: http://old.nabble.com/Can-the-site.xml-inheritance-be-avoided---tp27556750p27556750.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: SureFire: "parallel" attribute
Anybody? On Feb 10, 2010, at 6:10 PM, Douglas Ferguson wrote: > Can anybody shed light on this comment? > > .. > > parallel > > String2.2 (TestNG only) When you use the parallel attribute, > TestNG will try to run all your test methods in separate threads, except for > methods that depend on each other, which will be run in the same thread > in order to respect their order of execution. > > In JUnit 4.7 the values are classes/methods/both to run in separate > threads, as controlled by threadCount. > > . > > I have junit test tests and when I set parallel = methods it runs everything > synchronously, however when I set parallel = classes, it runs the classes in > parallel. I haven't been able to find good documentation for this anywhere.. > Does anybody know of any good resources? > > Also, assuming I can get methods to work, does it run all methods in parallel > or does it run the methods in parallel by class? i.e. 1 class at a time but > all the methods in that class are parallel? > > Are there other gotchas or configuration settings I should be considering? > I.E. I've read a little bit on ConfigurableParallelComputer but I'm not sure > what it's all about.. > > Douglas Ferguson > > mobile: 512.293.7279 > office/fax: 512.462.0408 > skype: stillrecording > aim: DaAmericanRuse > > - > > http://www.linkedin.com/in/douglasferguson > http://www.myspace.com/douglasferguson > http://www.douglasferguson.us/ > http://www.distilleryrecords.com/ > http://www.stillrecording.com/ > > Join my mailing list: distilleryrecords-subscr...@yahoogroups.com > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Including generated jars into ear file
Works fine Wayne. Thanks for your help Wayne Fay wrote: > >> Missing: >> -- >> 1) xxx:mytranslets:jar:1.0 > > 1. Build from parent/top project and Maven will automatically resolve > the missing artifact. > 2. Run "mvn install" on module so the jars are copied to your local repo > cache. > > Wayne > > - > 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/Including-generated-jars-into-ear-file-tp27495491p27556671.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.build.timestamp Not Interpolated
You got it. I had ${maven.build.timestamp} instead of just ${timestamp}. I
caught it right after I sent the E-mail. A brilliant move on my part!
Thanks for your help.
On Feb 11, 2010, at 5:11 PM, Eric Chatellier wrote:
>
>> Thanks for the prompt response, Eric. I added the following to my pom:
>>
>>
>> ${maven.build.timestamp}
>>
>> It is now one of several properties, but it still isn't being referenced
>> for me in my config file. I am using Maven 2.2.1.
>>
>> All other properties are interpolated correctly. I am sure I am missing
>> something silly. Any further insight is appreciated.
>
> It's hard to known what is missing now :)
>
> Have you set filtering=true in
>
>
>src/main/resources
>true
>
>
> ?
>
> Have you set ${timestamp} instead of ${maven.build.timestamp} ?
>
> --
> Éric Chatellier
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven.build.timestamp Not Interpolated
> Thanks for the prompt response, Eric. I added the following to my pom:
>
>
> ${maven.build.timestamp}
>
> It is now one of several properties, but it still isn't being referenced
> for me in my config file. I am using Maven 2.2.1.
>
> All other properties are interpolated correctly. I am sure I am missing
> something silly. Any further insight is appreciated.
It's hard to known what is missing now :)
Have you set filtering=true in
src/main/resources
true
?
Have you set ${timestamp} instead of ${maven.build.timestamp} ?
--
Éric Chatellier
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven.build.timestamp Not Interpolated
Thanks for the prompt response, Eric. I added the following to my pom:
${maven.build.timestamp}
It is now one of several properties, but it still isn't being referenced for me
in my config file. I am using Maven 2.2.1.
All other properties are interpolated correctly. I am sure I am missing
something silly. Any further insight is appreciated.
Thanks.
On Feb 11, 2010, at 4:45 PM, Eric Chatellier wrote:
The subject pretty much says it all. I have included this property in a
config file, but it isn't being interpolated. Do I need a special plugin
to have this value be recognized? Or if this is dated, how can I get the
timestamp for the build?
Hi,
There is an open bug report about this property.
http://jira.codehaus.org/browse/MRESOURCES-99
Workarround works fine.
--
Éric Chatellier
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven.build.timestamp Not Interpolated
> The subject pretty much says it all. I have included this property in a > config file, but it isn't being interpolated. Do I need a special plugin > to have this value be recognized? Or if this is dated, how can I get the > timestamp for the build? Hi, There is an open bug report about this property. http://jira.codehaus.org/browse/MRESOURCES-99 Workarround works fine. -- Éric Chatellier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven.build.timestamp Not Interpolated
The subject pretty much says it all. I have included this property in a config file, but it isn't being interpolated. Do I need a special plugin to have this value be recognized? Or if this is dated, how can I get the timestamp for the build? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: repository replication
What repo manager are you using? Posting the question to that appropriate mailing list would make it possible to give you the correct answer. /Anders 2010/2/11 Smejkal Tomas > Hi, > > I have one repository on which four branches of our company are working and > I need to replicate it to local repository of each branch, can you give me > advise how to do it? Thanks for help.
Re: unwanted repository, how does maven locate it
I had filed https://issues.apache.org/bugzilla/show_bug.cgi?id=48216 against log4j to mark javamail as optional (and it's still in NEW state) but yes, log4j should mark all those optional dependencies as so. Kalle On Wed, Feb 10, 2010 at 12:24 PM, Reto Bachmann-Gmür wrote: > ok, the evil-doer is > > http://repo2.maven.org/maven2/log4j/log4j/1.2.15/log4j-1.2.15.pom > > it was a bit tricky to find as an older harmless version of it showed up in > the dependency tree. Others are having the problem as well: > http://jira.codehaus.org/browse/MEV-649 > > Cheers, > reto > > On Wed, Feb 10, 2010 at 7:57 PM, Reto Bachmann-Gmür wrote: > >> thanks for the reply. I tried looking for this and found that >> >> http://repo2.maven.org/maven2/com/hp/hpl/jena/arq/2.8.2/arq-2.8.2.pom >> >> references another repo, but its not the dev.java.net one. I assumed for >> the repository to be used it would have to be defined on the path to the >> dependency, or can it be just anywhere? >> >> an extract from the output of the build process: >> >> ... >> [INFO] snapshot >> org.apache.clerezza:org.apache.clerezza.rdf.jena.storage:0.5-incubating-SNAPSHOT: >> checking for updates from ops4j >> [INFO] snapshot >> org.apache.clerezza:org.apache.clerezza.rdf.jena.storage:0.5-incubating-SNAPSHOT: >> checking for updates from apache >> [WARNING] POM for 'javax.jms:jms:pom:1.1:compile' is invalid. >> >> Its dependencies (if any) will NOT be available to the current build. >> Downloading: >> http://repository.ops4j.org/mvn-snapshots//com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.pom >> [INFO] Unable to find resource 'com.sun.jmx:jmxri:pom:1.2.1' in repository >> ops4j (http://repository.ops4j.org/mvn-snapshots/) >> Downloading: >> http://repository.apache.org/content/groups/snapshots-group/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.pom >> [INFO] Unable to find resource 'com.sun.jmx:jmxri:pom:1.2.1' in repository >> apache (http://repository.apache.org/content/groups/snapshots-group) >> Downloading: >> http://openjena.org/repo/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.pom >> [INFO] Unable to find resource 'com.sun.jmx:jmxri:pom:1.2.1' in repository >> repo-jena (http://openjena.org/repo) >> Downloading: >> http://openjena.org/repo-dev/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.pom >> [INFO] Unable to find resource 'com.sun.jmx:jmxri:pom:1.2.1' in repository >> repo-jena-dev (http://openjena.org/repo-dev) >> Downloading: >> https://maven-repository.dev.java.net/nonav/repository/com.sun.jmx/poms/jmxri-1.2.1.pom >> 353b downloaded (jmxri-1.2.1.pom) >> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = >> 'de02d09af9d9fd6ebe64712281899f4765ff4bd7'; remote = '> Downloading: >> https://maven-repository.dev.java.net/nonav/repository/com.sun.jmx/poms/jmxri-1.2.1.pom >> 353b downloaded (jmxri-1.2.1.pom) >> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = >> 'de02d09af9d9fd6ebe64712281899f4765ff4bd7'; remote = '> [WARNING] POM for 'com.sun.jmx:jmxri:pom:1.2.1:compile' is invalid. >> >> Its dependencies (if any) will NOT be available to the current build. >> [INFO] snapshot >> org.apache.clerezza:org.apache.clerezza.rdf.core.test:0.13-incubating-SNAPSHOT: >> checking for updates from ops4j >> ... >> >> any hint on how to locate the evil doing pom? >> >> Cheers, >> reto >> >> >> >> On Wed, Feb 10, 2010 at 7:45 PM, Todd Thiessen wrote: >> >>> A pom you depend on my have defined it in its pom. To be absolutely sure >>> you only reference the repos you want, you would need to mirror all repos to >>> your own trusted local repository using a repo manager. >>> >>> Good discussion about that here: >>> >>> >>> http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/ >>> >>> --- >>> Todd Thiessen >>> >>> >>> > -Original Message- >>> > From: Reto Bachmann-Gmür [mailto:r...@gmuer.ch] >>> > Sent: Wednesday, February 10, 2010 1:40 PM >>> > To: Maven Users List >>> > Subject: unwanted repository, how does maven locate it >>> > >>> > hello >>> > >>> > I have the following problem using maven 2.2.1 (on >>> > minerva.apache.org): >>> > maven continuos to download a broken jar and pom from >>> > https://maven-repository.dev.java.net/nonav/repository/com.sun >>> > .jmx/jars/ >>> > >>> > Th epatch to the dependency is as follows: >>> > [INFO] +- com.hp.hpl.jena:tdb:jar:0.8.4:compile >>> > [INFO] | \- com.hp.hpl.jena:arq:jar:2.8.2:compile >>> > [INFO] | +- org.codehaus.woodstox:wstx-asl:jar:3.2.9:compile >>> > [INFO] | | \- stax:stax-api:jar:1.0.1:compile >>> > [INFO] | +- org.apache.lucene:lucene-core:jar:2.3.1:compile >>> > [INFO] | +- org.slf4j:slf4j-log4j12:jar:1.5.6:compile >>> > [INFO] | \- log4j:log4j:jar:1.2.14:compile >>> > [INFO] | +- javax.mail:mail:jar:1.4:compile >>> > [INFO] | +- javax.jms:jms:jar:1.1:compile >>> > [INFO] | +- com.sun.jdmk:jmxtools:jar:1.2.1:compile >>> > [INFO] | \- com.sun.jmx:jmxri:jar:1.2.1:compile >>> > >>> > the dev.java.net repositor
[ANN] Maven Release Plugin 2.0 Released
The Maven team is pleased to announce the release of the Maven Release Plugin, version 2.0. This release also includes Maven Release Manager, version 2.0. This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. http://maven.apache.org/plugins/maven-release-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-release-plugin 2.0 Release Notes - Maven 2.x Release Plugin - Version 2.0 ** Bug * [MRELEASE-3] - release:prepare should not require multimodule artifacts to be in the local repository * [MRELEASE-278] - release:clean doesn't clean up after release:branch * [MRELEASE-322] - Unable to set the working directory for projects where the master pom isn't at the root of the project * [MRELEASE-327] - Is branchName really optional for release:branch ? If so, what is the default? * [MRELEASE-336] - unable to release:prepare flat hierarchy project * [MRELEASE-383] - svn inconsistent line ending style * [MRELEASE-387] - command line versions don't seem to work on release:branch * [MRELEASE-389] - Properties releaseVersion and developmentVersion are not read correctly during release:prepare (eventually release:perform) * [MRELEASE-433] - Add parameter remoteTagging to release:branch (to prevent issue with svn > 1.5.0) * [MRELEASE-442] - scm tag phase ignores custom message (need to use scm 1.3) * [MRELEASE-452] - allowTimestampedSnapshots=true still fails with snapshot dependencies * [MRELEASE-460] - Please upgrade to JDOM 1.1; current JDOM 1.0 contains a bug in parsing comments starting with hyphen * [MRELEASE-481] - prepare goal no longer errors on subversion files * [MRELEASE-493] - Prepare step doesn't stop if there are modified local files * [MRELEASE-502] - fix the equals() and hashCode() functions in release-descriptor.mdo * [MRELEASE-515] - release:prepare eats the root cause of the exception * [MRELEASE-520] - A comma separated list of release goals causes the release:perform goal to fail ** Improvement * [MRELEASE-225] - release should support multi-module project with sibling subprojects * [MRELEASE-261] - release:prepare should support flat directory multi-module projects * [MRELEASE-291] - FAQ entry explaining how to release a parent pom without releasing it's modules * [MRELEASE-324] - There should be a way to update POM version numbers without tagging/branching * [MRELEASE-377] - Missing releaseVersion parameter in release:branch goal * [MRELEASE-422] - Output the resulting tag name or branch name during dryRun * [MRELEASE-423] - Wrong goal specified to generate a release pom * [MRELEASE-451] - CLONE -scm:tag with scmCommentPrefix * [MRELEASE-461] - Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0) in branch mojo * [MRELEASE-475] - Don't print stack trace when release:branch finds uncommitted files. * [MRELEASE-505] - Upgrade to scm 1.3 ** New Feature * [MRELEASE-372] - add branchBase optional parameter for release:branch goal * [MRELEASE-501] - create the possibility for performing a local checkout instead a clean checkout from the upstream repository for DSCMs * [MRELEASE-508] - Add TFS support Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
repository replication
Hi, I have one repository on which four branches of our company are working and I need to replicate it to local repository of each branch, can you give me advise how to do it? Thanks for help.
maven-release-plugin, svn and tagging
hello, I am facing an issue when wanting to release an artifact with the maven-release-plugin. After some searching I figured the problem had already been reported on JIRA, and I added one comment with more detailed stacktraces about it (http://jira.codehaus.org/browse/MRELEASE-492). Out of curiosity, I was wondering if other people here might have encountered the same issue, and if there is perhaps a workaround for this? Thanks, Manuel - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: unit testing archetypes
Good stuff Luke, thanks, I've been pondering what the best approach is
for this myself.
Kalle
On Thu, Feb 11, 2010 at 6:13 AM, Luke Patterson
wrote:
> On Wed, Feb 10, 2010 at 5:37 PM, Max Spring wrote:
>> What would be a good approach to test an archetype project?
>> ...
>> A minimal test would be to "instantiate" the archetype and to build the
>> resulting project.
>
> Here's some cut-and-paste that I'm using:
>
>
> org.apache.maven.plugins
> maven-invoker-plugin
>
>
> integration-test
>
> install
> run
>
>
>
>
> ${project.build.directory}/it/projects
>
> org.apache.maven.plugins:maven-archetype-plugin:generate
>
> ${project.build.directory}/it/repo
>
> *
>
> ${basedir}/src/it/projects
>
> ${project.artifactId}
> ${project.groupId}
> local
> ${project.version}
> verify
> false
>
> true
>
>
>
>
> then, your archetype will be run during integration-test phase for all
> subdirectories of , a test.properties file will
> contain the inputs to the archetype:generate goal, and the verify
> phase will be run on each newly generated project
>
> to add a new test, add another directory under
> with a test.properties file
>
> --
> e.g.
>
> src/it/projects/firsttest/test.properties with contents:
>
> groupId=com.foo
> artifactId=firsttest
> version=1.0.0
> package=com.foo.firsttest
>
> that will create a "firsttest" directory under
> ${project.build.directory}/it/projects/firsttest with the stuff
> generated by your archetype, and then run the verify phase on the
> newly generated "com.foo.firsttest" project
> --
>
> -
> 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: Deploying assembly package with maven-release-plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anders Hammar wrote: > Wrong goal. Use single instead! > Clearly stated in the docs...:-) > Thx Anders Sometimes the simple solutions are the hardest to find :D I was looking more into the release- and deploy-plugin to find out how to get these to upload my generated artifact. Meanwhile I got it also working with the maven-build-helper-plugin, but your suggestion was exactly what I was looking for. You made my day ;) - -- Linkwerk - Software und Beratung für vernetzte Information Telefon: +49 40 69 66 48 14 Web: www.linkwerk.com Linkwerk GmbH, Oberaltenallee 20a, 22081 Hamburg, Handelsregister Hamburg, HRB 95084 Geschäftsführer: Stefan Mintert -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkt0JOgACgkQSm4S1ty9BPWFlgCfeGzDHKXtNX3D1SwuvRqntSCO FhUAmwQlljqBQwmp+HbmK8MM6MjgaS57 =bCU3 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Regarding coping the dependencies
Hi All, I know copy dependencies goal copy all the direct dependency as well as transitive.i want to copy one lavel transitive of one particular dependent plugin. suppose i am having 5 dependencies.meaning all the 5 will be copied as well as dependencies of one among the 5 also will be copied. can i achieve the same with the dependency plugin? Thanks, Debasis -- View this message in context: http://old.nabble.com/Regarding-coping-the-dependencies-tp27547619p27547619.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
Enforce property existence before dependency resolution
Hi,
I am using Maven in the context of the build of a cross-plateform C++
application.
It means that, in my own Maven repository, I have zip-artifacts containing
several DLL or so files like:
boost:boost_regex:1.34.1:zip
In order to distinguish between plateforms, I use the classifier and I
actually have these artifacts:
boost:boost_regex:1.34.1:zip:x86-windows-vc8
or:
boost:boost_regex:1.34.1:zip:x86-linux2.6-gcc3.3
That's to say I have 1 zip for windows, another one for linux...
It means that the dependency section of my POM looks like:
boost_regex
boost_regex
1.34.1
${target.platform}
zip
This works great if I specify a -Dtarget.plateform=x86-linux2.6-gcc3.3
option on Maven command-line.
I would like to use the enforcer plugin to ensure that the "target.platform"
property has been defined before running the build.
However it seems that the dependency resolution comes before the execution
of enforcer. In the end, when I "forget" the property on the command-line, I
don't get an explicit error message from enforcer but rather a Maven message
telling me that the boost:boost_regex:1.34.1:zip:${target.platform} does not
exist.
Do you know how I can make sure that the ${target.platform} property has
been defined before running into the dependency resolution process?
I've tried several things (like putting the enforcer in a parent POM of my
current POM) but none of them worked.
Many thanks in advance for your answers,
Cheers,
Bruno.
--
View this message in context:
http://old.nabble.com/Enforce-property-existence-before-dependency-resolution-tp27547470p27547470.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-nar-plugin (http://duns.github.com/maven-nar-plugin)
Its been a long time since I used it but when I did I had two problems. It could not handle the concept of different msvc compiler versions, it just used whatever it found if I recall. It could not handle the new universal binaries on OS X. Other than these issues it seemed good but these issues were roadblocks at the time for us. -Dave On Thu, Feb 11, 2010 at 2:11 AM, Karl Heinz Marbaise wrote: > > So it seemed to be a little bit early... > > I have changed the layout of my files: > . > |-- pom.xml > `-- src >|-- main >| |-- c++ >| | `-- bruch.cxx > | `-- include >| `-- bruch.hxx > `-- test >`-- c++ >`-- bruch_test.cxx > > > and now the usual call mvn test or mvn package work like a charm... > > Wow cool... > > Kind regards > Karl Heinz Marbaise > -- > View this message in context: > http://old.nabble.com/maven-nar-plugin-%28http%3A--duns.github.com-maven-nar-plugin%29-tp27543417p27544174.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: Deploying assembly package with maven-release-plugin
Wrong goal. Use single instead! Clearly stated in the docs...:-) /Anders On Thu, Feb 11, 2010 at 14:46, Bastian Spanneberg < bastian.spanneb...@linkwerk.com> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi everybody > > We use Hudson and the maven-release-plugin to do our release builds. Now > I have a project which contains an assembly that puts together all > needed components and then packages them into a .tar.gz package with the > desired directory structure. > > Now I'm trying to get the release-plugin to deploy this package to our > Maven repository during the release:perform goal, but only the standard > stuff (sources, javadoc, POM) are deployed. > > I've already bound the assembly goal to the maven package phase, and the > .tar.gz gets built during the release:perform, but not uploaded to the > repository. > > Any hints what might be wrong here ? > > - -- > Linkwerk - Software und Beratung für vernetzte Information > Telefon: +49 40 69 66 48 14 > Web: www.linkwerk.com > > Linkwerk GmbH, Oberaltenallee 20a, 22081 Hamburg, > Handelsregister Hamburg, HRB 95084 > Geschäftsführer: Stefan Mintert > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkt0CiQACgkQSm4S1ty9BPUROACeLzUhQkxDCZ8KOTScDatMGSwt > 4zgAnjycDx8JVxRdv++4W+oiMjWjpkab > =0YA8 > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: unit testing archetypes
On Wed, Feb 10, 2010 at 5:37 PM, Max Spring wrote:
> What would be a good approach to test an archetype project?
> ...
> A minimal test would be to "instantiate" the archetype and to build the
> resulting project.
Here's some cut-and-paste that I'm using:
org.apache.maven.plugins
maven-invoker-plugin
integration-test
install
run
${project.build.directory}/it/projects
org.apache.maven.plugins:maven-archetype-plugin:generate
${project.build.directory}/it/repo
*
${basedir}/src/it/projects
${project.artifactId}
${project.groupId}
local
${project.version}
verify
false
true
then, your archetype will be run during integration-test phase for all
subdirectories of , a test.properties file will
contain the inputs to the archetype:generate goal, and the verify
phase will be run on each newly generated project
to add a new test, add another directory under
with a test.properties file
--
e.g.
src/it/projects/firsttest/test.properties with contents:
groupId=com.foo
artifactId=firsttest
version=1.0.0
package=com.foo.firsttest
that will create a "firsttest" directory under
${project.build.directory}/it/projects/firsttest with the stuff
generated by your archetype, and then run the verify phase on the
newly generated "com.foo.firsttest" project
--
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Deploying assembly package with maven-release-plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everybody We use Hudson and the maven-release-plugin to do our release builds. Now I have a project which contains an assembly that puts together all needed components and then packages them into a .tar.gz package with the desired directory structure. Now I'm trying to get the release-plugin to deploy this package to our Maven repository during the release:perform goal, but only the standard stuff (sources, javadoc, POM) are deployed. I've already bound the assembly goal to the maven package phase, and the .tar.gz gets built during the release:perform, but not uploaded to the repository. Any hints what might be wrong here ? - -- Linkwerk - Software und Beratung für vernetzte Information Telefon: +49 40 69 66 48 14 Web: www.linkwerk.com Linkwerk GmbH, Oberaltenallee 20a, 22081 Hamburg, Handelsregister Hamburg, HRB 95084 Geschäftsführer: Stefan Mintert -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkt0CiQACgkQSm4S1ty9BPUROACeLzUhQkxDCZ8KOTScDatMGSwt 4zgAnjycDx8JVxRdv++4W+oiMjWjpkab =0YA8 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Question about http://repository.sonatype.org/content/groups/forge/
I think you should move this discussion to the nexus user list and ask the sonatype people there what they suggest. /Anders On Thu, Feb 11, 2010 at 13:44, Karl Heinz Marbaise wrote: > Hi Anders, > > may be i was a little bit inaccurate... > > In that repository i can find snapshot versions of e.g. > http://repository.sonatype.org/content/groups/forge/org/apache/maven/plugins/maven-help-plugin/which > causes sometimes problems on my site...(may be a misconfiguration on > my site?..)... > > If i add this repository to my nexus (company) i got the snapshot versions > as well so if i see it well it's not possible to configure in that way to > have only the non snapshot versions (in my case the nexus artifacts)...cause > in the other repository of that nexus instance ( > http://repository.sonatype.org/content/repositories/central/) i can find > only nexus till release 1.3.6 nothing newer... > > May be there is a possibility in nexus to fix this problem... > > Thanks for your help. > > Kind regards > Karl Heinz Marbaise > > Original-Nachricht > > Datum: Thu, 11 Feb 2010 12:08:55 +0100 > > Von: Anders Hammar > > An: Maven Users List > > Betreff: Re: Question about > http://repository.sonatype.org/content/groups/forge/ > > > Yes, there are Nexus snapshots there as well. And I'm pretty sure that is > > official. > > Not sure about your question - is there a "not" missing in the text? > > > > /Anders > > > > On Thu, Feb 11, 2010 at 11:22, Karl Heinz Marbaise > wrote: > > > > > > > > Hi, > > > > > > i just want to know if the above repository (where nexus is available > as > > > artifact) is for snapshot's as well officially...cause in this repo i > > can > > > find snapshot artifacts e.g. org/apache/maven/plugins/maven-help-plugin > > > May be i have to use a different repo for nexus artifacts... > > > > > > Thanks in advance... > > > Kind regards > > > Karl Heinz Marbaise > > > -- > > > View this message in context: > > > > > > http://old.nabble.com/Question-about-http%3A--repository.sonatype.org-content-groups-forge--tp27544306p27544306.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 > > > > > > > > -- > MfG > Karl Heinz Marbaise > -- > SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 > Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 > Hauptstrasse 177 USt.IdNr: DE191347579 > 52146 Würselen http://www.soebes.de > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Question about http://repository.sonatype.org/content/groups/forge/
Hi Anders, may be i was a little bit inaccurate... In that repository i can find snapshot versions of e.g. http://repository.sonatype.org/content/groups/forge/org/apache/maven/plugins/maven-help-plugin/ which causes sometimes problems on my site...(may be a misconfiguration on my site?..)... If i add this repository to my nexus (company) i got the snapshot versions as well so if i see it well it's not possible to configure in that way to have only the non snapshot versions (in my case the nexus artifacts)...cause in the other repository of that nexus instance (http://repository.sonatype.org/content/repositories/central/) i can find only nexus till release 1.3.6 nothing newer... May be there is a possibility in nexus to fix this problem... Thanks for your help. Kind regards Karl Heinz Marbaise Original-Nachricht > Datum: Thu, 11 Feb 2010 12:08:55 +0100 > Von: Anders Hammar > An: Maven Users List > Betreff: Re: Question about > http://repository.sonatype.org/content/groups/forge/ > Yes, there are Nexus snapshots there as well. And I'm pretty sure that is > official. > Not sure about your question - is there a "not" missing in the text? > > /Anders > > On Thu, Feb 11, 2010 at 11:22, Karl Heinz Marbaise wrote: > > > > > Hi, > > > > i just want to know if the above repository (where nexus is available as > > artifact) is for snapshot's as well officially...cause in this repo i > can > > find snapshot artifacts e.g. org/apache/maven/plugins/maven-help-plugin > > May be i have to use a different repo for nexus artifacts... > > > > Thanks in advance... > > Kind regards > > Karl Heinz Marbaise > > -- > > View this message in context: > > > http://old.nabble.com/Question-about-http%3A--repository.sonatype.org-content-groups-forge--tp27544306p27544306.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 > > > > -- MfG Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Question about http://repository.sonatype.org/content/groups/forge/
Yes, there are Nexus snapshots there as well. And I'm pretty sure that is official. Not sure about your question - is there a "not" missing in the text? /Anders On Thu, Feb 11, 2010 at 11:22, Karl Heinz Marbaise wrote: > > Hi, > > i just want to know if the above repository (where nexus is available as > artifact) is for snapshot's as well officially...cause in this repo i can > find snapshot artifacts e.g. org/apache/maven/plugins/maven-help-plugin > May be i have to use a different repo for nexus artifacts... > > Thanks in advance... > Kind regards > Karl Heinz Marbaise > -- > View this message in context: > http://old.nabble.com/Question-about-http%3A--repository.sonatype.org-content-groups-forge--tp27544306p27544306.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: unit testing archetypes
maven invoker plugin On 10 February 2010 23:37, Max Spring wrote: > What would be a good approach to test an archetype project? > I'd like to have the test attached as a "unit" test to the archetype project > itself. > A minimal test would be to "instantiate" the archetype and to build the > resulting project. > So far I have been playing with the exec-maven-plugin to invoke Maven > recursively, in the install phase. > I have to do this in the install phase in order for the archetype to be > visible. > It doesn't look very elegant to me. > Is there a better way to do this? > Thanks! > -Max > > > - > 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
Question about http://repository.sonatype.org/content/groups/forge/
Hi, i just want to know if the above repository (where nexus is available as artifact) is for snapshot's as well officially...cause in this repo i can find snapshot artifacts e.g. org/apache/maven/plugins/maven-help-plugin May be i have to use a different repo for nexus artifacts... Thanks in advance... Kind regards Karl Heinz Marbaise -- View this message in context: http://old.nabble.com/Question-about-http%3A--repository.sonatype.org-content-groups-forge--tp27544306p27544306.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: The plugin 'org.apache.maven.plugins:maven-install-plugin' does not exist
As a started, try following the instructions: "For more information, run Maven with the -e switch" That might give you a clue why it doesn't work. If not, ask here again. Also, any changes to the environment between the working execution and the non-working? /Anders On Wed, Feb 10, 2010 at 20:55, oneofthelions wrote: > > Hi, > > I was able to run mvn clean install till last night, but don't know what > happened the mvn is not recognized anymore. I am using mvn as build tool, > RSA as IDE(same as eclipse) and weblogic as my application server. Any idea > why the below error occurs > > [WARNING] repository metadata for: 'artifact > org.apache.maven.plugins:maven-install-plugin' could not be retrieved from > repository: central due to an error: Error transferring file > [INFO] Repository 'central' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-install-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 3 seconds > [INFO] Finished at: Wed Feb 10 14:46:29 EST 2010 > [INFO] Final Memory: 46M/64M > [INFO] > > -- > View this message in context: > http://n2.nabble.com/The-plugin-org-apache-maven-plugins-maven-install-plugin-does-not-exist-tp4550382p4550382.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 > >
The plugin 'org.apache.maven.plugins:maven-install-plugin' does not exist
Hi, I was able to run mvn clean install till last night, but don't know what happened the mvn is not recognized anymore. I am using mvn as build tool, RSA as IDE(same as eclipse) and weblogic as my application server. Any idea why the below error occurs [WARNING] repository metadata for: 'artifact org.apache.maven.plugins:maven-install-plugin' could not be retrieved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-install-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Wed Feb 10 14:46:29 EST 2010 [INFO] Final Memory: 46M/64M [INFO] -- View this message in context: http://n2.nabble.com/The-plugin-org-apache-maven-plugins-maven-install-plugin-does-not-exist-tp4550382p4550382.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: unwanted repository, how does maven locate it
thanks for the reply. I tried looking for this and found that http://repo2.maven.org/maven2/com/hp/hpl/jena/arq/2.8.2/arq-2.8.2.pom references another repo, but its not the dev.java.net one. I assumed for the repository to be used it would have to be defined on the path to the dependency, or can it be just anywhere? an extract from the output of the build process: ... [INFO] snapshot org.apache.clerezza:org.apache.clerezza.rdf.jena.storage:0.5-incubating-SNAPSHOT: checking for updates from ops4j [INFO] snapshot org.apache.clerezza:org.apache.clerezza.rdf.jena.storage:0.5-incubating-SNAPSHOT: checking for updates from apache [WARNING] POM for 'javax.jms:jms:pom:1.1:compile' is invalid. Its dependencies (if any) will NOT be available to the current build. Downloading: http://repository.ops4j.org/mvn-snapshots//com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.pom [INFO] Unable to find resource 'com.sun.jmx:jmxri:pom:1.2.1' in repository ops4j (http://repository.ops4j.org/mvn-snapshots/) Downloading: http://repository.apache.org/content/groups/snapshots-group/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.pom [INFO] Unable to find resource 'com.sun.jmx:jmxri:pom:1.2.1' in repository apache (http://repository.apache.org/content/groups/snapshots-group) Downloading: http://openjena.org/repo/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.pom [INFO] Unable to find resource 'com.sun.jmx:jmxri:pom:1.2.1' in repository repo-jena (http://openjena.org/repo) Downloading: http://openjena.org/repo-dev/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.pom [INFO] Unable to find resource 'com.sun.jmx:jmxri:pom:1.2.1' in repository repo-jena-dev (http://openjena.org/repo-dev) Downloading: https://maven-repository.dev.java.net/nonav/repository/com.sun.jmx/poms/jmxri-1.2.1.pom 353b downloaded (jmxri-1.2.1.pom) [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'de02d09af9d9fd6ebe64712281899f4765ff4bd7'; remote = 'https://maven-repository.dev.java.net/nonav/repository/com.sun.jmx/poms/jmxri-1.2.1.pom 353b downloaded (jmxri-1.2.1.pom) [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'de02d09af9d9fd6ebe64712281899f4765ff4bd7'; remote = ' wrote: > A pom you depend on my have defined it in its pom. To be absolutely sure > you only reference the repos you want, you would need to mirror all repos to > your own trusted local repository using a repo manager. > > Good discussion about that here: > > > http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/ > > --- > Todd Thiessen > > > > -Original Message- > > From: Reto Bachmann-Gmür [mailto:r...@gmuer.ch] > > Sent: Wednesday, February 10, 2010 1:40 PM > > To: Maven Users List > > Subject: unwanted repository, how does maven locate it > > > > hello > > > > I have the following problem using maven 2.2.1 (on > > minerva.apache.org): > > maven continuos to download a broken jar and pom from > > https://maven-repository.dev.java.net/nonav/repository/com.sun > > .jmx/jars/ > > > > Th epatch to the dependency is as follows: > > [INFO] +- com.hp.hpl.jena:tdb:jar:0.8.4:compile > > [INFO] | \- com.hp.hpl.jena:arq:jar:2.8.2:compile > > [INFO] | +- org.codehaus.woodstox:wstx-asl:jar:3.2.9:compile > > [INFO] | | \- stax:stax-api:jar:1.0.1:compile > > [INFO] | +- org.apache.lucene:lucene-core:jar:2.3.1:compile > > [INFO] | +- org.slf4j:slf4j-log4j12:jar:1.5.6:compile > > [INFO] | \- log4j:log4j:jar:1.2.14:compile > > [INFO] |+- javax.mail:mail:jar:1.4:compile > > [INFO] |+- javax.jms:jms:jar:1.1:compile > > [INFO] |+- com.sun.jdmk:jmxtools:jar:1.2.1:compile > > [INFO] |\- com.sun.jmx:jmxri:jar:1.2.1:compile > > > > the dev.java.net repository is neither in my pom, nor its > > parent nor in a settings.xml file, any idea why maven tries > > to download artifacts from there? > > > > cheers > > reto > > > > > > - > > 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: unwanted repository, how does maven locate it
ok, the evil-doer is http://repo2.maven.org/maven2/log4j/log4j/1.2.15/log4j-1.2.15.pom it was a bit tricky to find as an older harmless version of it showed up in the dependency tree. Others are having the problem as well: http://jira.codehaus.org/browse/MEV-649 Cheers, reto On Wed, Feb 10, 2010 at 7:57 PM, Reto Bachmann-Gmür wrote: > thanks for the reply. I tried looking for this and found that > > http://repo2.maven.org/maven2/com/hp/hpl/jena/arq/2.8.2/arq-2.8.2.pom > > references another repo, but its not the dev.java.net one. I assumed for > the repository to be used it would have to be defined on the path to the > dependency, or can it be just anywhere? > > an extract from the output of the build process: > > ... > [INFO] snapshot > org.apache.clerezza:org.apache.clerezza.rdf.jena.storage:0.5-incubating-SNAPSHOT: > checking for updates from ops4j > [INFO] snapshot > org.apache.clerezza:org.apache.clerezza.rdf.jena.storage:0.5-incubating-SNAPSHOT: > checking for updates from apache > [WARNING] POM for 'javax.jms:jms:pom:1.1:compile' is invalid. > > Its dependencies (if any) will NOT be available to the current build. > Downloading: > http://repository.ops4j.org/mvn-snapshots//com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.pom > [INFO] Unable to find resource 'com.sun.jmx:jmxri:pom:1.2.1' in repository > ops4j (http://repository.ops4j.org/mvn-snapshots/) > Downloading: > http://repository.apache.org/content/groups/snapshots-group/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.pom > [INFO] Unable to find resource 'com.sun.jmx:jmxri:pom:1.2.1' in repository > apache (http://repository.apache.org/content/groups/snapshots-group) > Downloading: > http://openjena.org/repo/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.pom > [INFO] Unable to find resource 'com.sun.jmx:jmxri:pom:1.2.1' in repository > repo-jena (http://openjena.org/repo) > Downloading: > http://openjena.org/repo-dev/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.pom > [INFO] Unable to find resource 'com.sun.jmx:jmxri:pom:1.2.1' in repository > repo-jena-dev (http://openjena.org/repo-dev) > Downloading: > https://maven-repository.dev.java.net/nonav/repository/com.sun.jmx/poms/jmxri-1.2.1.pom > 353b downloaded (jmxri-1.2.1.pom) > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > 'de02d09af9d9fd6ebe64712281899f4765ff4bd7'; remote = ' Downloading: > https://maven-repository.dev.java.net/nonav/repository/com.sun.jmx/poms/jmxri-1.2.1.pom > 353b downloaded (jmxri-1.2.1.pom) > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > 'de02d09af9d9fd6ebe64712281899f4765ff4bd7'; remote = ' [WARNING] POM for 'com.sun.jmx:jmxri:pom:1.2.1:compile' is invalid. > > Its dependencies (if any) will NOT be available to the current build. > [INFO] snapshot > org.apache.clerezza:org.apache.clerezza.rdf.core.test:0.13-incubating-SNAPSHOT: > checking for updates from ops4j > ... > > any hint on how to locate the evil doing pom? > > Cheers, > reto > > > > On Wed, Feb 10, 2010 at 7:45 PM, Todd Thiessen wrote: > >> A pom you depend on my have defined it in its pom. To be absolutely sure >> you only reference the repos you want, you would need to mirror all repos to >> your own trusted local repository using a repo manager. >> >> Good discussion about that here: >> >> >> http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/ >> >> --- >> Todd Thiessen >> >> >> > -Original Message- >> > From: Reto Bachmann-Gmür [mailto:r...@gmuer.ch] >> > Sent: Wednesday, February 10, 2010 1:40 PM >> > To: Maven Users List >> > Subject: unwanted repository, how does maven locate it >> > >> > hello >> > >> > I have the following problem using maven 2.2.1 (on >> > minerva.apache.org): >> > maven continuos to download a broken jar and pom from >> > https://maven-repository.dev.java.net/nonav/repository/com.sun >> > .jmx/jars/ >> > >> > Th epatch to the dependency is as follows: >> > [INFO] +- com.hp.hpl.jena:tdb:jar:0.8.4:compile >> > [INFO] | \- com.hp.hpl.jena:arq:jar:2.8.2:compile >> > [INFO] | +- org.codehaus.woodstox:wstx-asl:jar:3.2.9:compile >> > [INFO] | | \- stax:stax-api:jar:1.0.1:compile >> > [INFO] | +- org.apache.lucene:lucene-core:jar:2.3.1:compile >> > [INFO] | +- org.slf4j:slf4j-log4j12:jar:1.5.6:compile >> > [INFO] | \- log4j:log4j:jar:1.2.14:compile >> > [INFO] |+- javax.mail:mail:jar:1.4:compile >> > [INFO] |+- javax.jms:jms:jar:1.1:compile >> > [INFO] |+- com.sun.jdmk:jmxtools:jar:1.2.1:compile >> > [INFO] |\- com.sun.jmx:jmxri:jar:1.2.1:compile >> > >> > the dev.java.net repository is neither in my pom, nor its >> > parent nor in a settings.xml file, any idea why maven tries >> > to download artifacts from there? >> > >> > cheers >> > reto >> > >> > >> > - >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: users-h...@maven.apache.org >> > >> > >> >> -
How to specify username for release plugin with Maven Scm 1.3 Git provider?
Release notes for Maven Scm 1.3 include the bug fix: * [*SCM*-516] - git provider doesn't respect *username* in settings.xml However, I can't mvn+scm+release+git to honour my settings file. I think my problem may lie with the id I'm using for the server, but I don't know what it should be. More details below. Please help. Richard In particular, I find this post confusing: http://markmail.org/message/upjecqichqtzuirg?q=scm+username+settings There is no obvious connection between the developerConnection and any of the server ids. (My release server settings for Nexus are picked up fine.) POM contains: org.apache.maven.plugins maven-scm-plugin 1.3 developerConnection My settings file contains: releases deployment ... developerConnection hoberman ...
unit testing archetypes
What would be a good approach to test an archetype project? I'd like to have the test attached as a "unit" test to the archetype project itself. A minimal test would be to "instantiate" the archetype and to build the resulting project. So far I have been playing with the exec-maven-plugin to invoke Maven recursively, in the install phase. I have to do this in the install phase in order for the archetype to be visible. It doesn't look very elegant to me. Is there a better way to do this? Thanks! -Max - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Accessing Properties in site.xml?
Yes... just do it. You need to be using a version of the site plugin >= 2.0-beta-6. For example: http://svn.apache.org/repos/asf/maven/site/trunk/src/site/site.xml - Brett On 11/02/2010, at 4:59 PM, mfs wrote: > > Hi Guys, > > Is there a way to access the properties defined in pom.xml from within > site.xml ?. I am creating some custom menu items and would like the "href" > for each of the items to be constructed dynamically based on some properties > in pom or within some profiles. > > Is that possible ? > > Thanks in advance, > Farhan > -- > View this message in context: > http://old.nabble.com/Accessing-Properties-in-site.xml--tp27542692p27542692.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 > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-nar-plugin (http://duns.github.com/maven-nar-plugin)
So it seemed to be a little bit early... I have changed the layout of my files: . |-- pom.xml `-- src |-- main | |-- c++ | | `-- bruch.cxx | `-- include | `-- bruch.hxx `-- test `-- c++ `-- bruch_test.cxx and now the usual call mvn test or mvn package work like a charm... Wow cool... Kind regards Karl Heinz Marbaise -- View this message in context: http://old.nabble.com/maven-nar-plugin-%28http%3A--duns.github.com-maven-nar-plugin%29-tp27543417p27544174.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
when using "copy-dependencies" goal in dependency plugin, how can i install old version to overwrite a new one
I'm trying to installer an older version of my project (to check rollback
option),
how can i tell maven to remove the new versions installed and replace with
older one?
the other way works perfect.
my pom:
org.apache.maven.plugins
maven-dependency-plugin
copy
install
copy
${project.groupId}
${project.artifactId}
${project.version}
${project.packaging}
true
${classpath}
copy-dependencies
install
copy-dependencies
${classpath}
true
true
true
false
--
Eyal Edri
Re: Getting the Profile Name From A Property
http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-listing-active-profiles.html /Anders On Wed, Feb 10, 2010 at 21:06, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > you can have multiple profiles active at the same time, so you need to ask > a slightly different question: either > > how do I tell if profile A is active? have profile A define a property eg > profile-A-active=true > > how do I get a list of all the active profiles? (I'm not sure about this > one) > > Sent from my [rhymes with tryPod] ;-) > > > On 10 Feb 2010, at 18:49, Neil Chaudhuri > wrote: > > Is there a built-in Maven property for obtaining the name of the profile >> currently active? >> >> Thanks. >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: unwanted repository, how does maven locate it
Reto Bachmann-Gmür wrote at Mittwoch, 10. Februar 2010 19:39: > hello > > I have the following problem using maven 2.2.1 (on minerva.apache.org): > maven continuos to download a broken jar and pom from > https://maven-repository.dev.java.net/nonav/repository/com.sun.jmx/jars/ > > Th epatch to the dependency is as follows: > [INFO] +- com.hp.hpl.jena:tdb:jar:0.8.4:compile > [INFO] | \- com.hp.hpl.jena:arq:jar:2.8.2:compile > [INFO] | +- org.codehaus.woodstox:wstx-asl:jar:3.2.9:compile > [INFO] | | \- stax:stax-api:jar:1.0.1:compile > [INFO] | +- org.apache.lucene:lucene-core:jar:2.3.1:compile > [INFO] | +- org.slf4j:slf4j-log4j12:jar:1.5.6:compile > [INFO] | \- log4j:log4j:jar:1.2.14:compile > [INFO] |+- javax.mail:mail:jar:1.4:compile > [INFO] |+- javax.jms:jms:jar:1.1:compile > [INFO] |+- com.sun.jdmk:jmxtools:jar:1.2.1:compile > [INFO] |\- com.sun.jmx:jmxri:jar:1.2.1:compile > > the dev.java.net repository is neither in my pom, nor its parent nor in > a settings.xml file, any idea why maven tries to download artifacts from > there? One of your deps define it in its (inherited) POM. All you can do to get rid of it is to define a global mirror in your settings.xml: maven-proxy Maven-Proxy for all repositories http://localhost/nexus *,!private-repo-release,!private-repo-snapshot, - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
