RE: Not a v4.0.0 POM error
Pardon me but usually the .pom is an xml text file. you should be able to open w/ text editor on ubuntu. try using vi or gedit. Sean -Original Message- From: Gerardo Corro [mailto:rob_gar_...@hotmail.com] Sent: Wednesday, November 11, 2009 5:11 PM To: users@maven.apache.org Subject: RE: Not a v4.0.0 POM error It's a valid pom: $ ls -l maven-install-plugin-2.3.pom -rw-r--r-- 1 corro corro 1486 2009-11-12 01:33 maven-install-plugin-2.3.pom $ file maven-install-plugin-2.3.pom maven-install-plugin-2.3.pom: gzip compressed data, from Unix $ gunzip -c maven-install-plugin-2.3.pom http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 and the file continues... however Ubuntu "Archive Manager Tool" can't extract it, it says the pom has errors. Best regards. > Date: Thu, 12 Nov 2009 01:21:26 +0100 > Subject: Re: Not a v4.0.0 POM error > From: nick.stolw...@gmail.com > To: users@maven.apache.org > > What do you see if you open it with a browser: > > https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugi > ns/maven-install-plugin/2.3/maven-install-plugin-2.3.pom > > Is it a valid pom or some garble? > > With regards, > > Nick Stolwijk > ~Java Developer~ > > IPROFS BV. > Claus Sluterweg 125 > 2012 WS Haarlem > http://www.iprofs.nl > > > > On Thu, Nov 12, 2009 at 12:19 AM, Gerardo Corro > wrote: > > > > Hi, > > > > Thanks for your message, however is not working :-( the same error is > > triggered again. > > > > Best regards > > > > > > > > > >> > >> I suggest you to delete the directory in your local repository > >> > >> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/ > >> > >> anyway, for me nothing to see with ubuntu (I works on it too) > >> > >> I already had such errors when a download of an artifact failed > >> (for multiple reason...) > >> > >> hope it will help you. > >> > >> Cheers, > >> > >> Tony. > >> > >> > > >> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: > >> > local = 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = ' > >> > ' - RETRYING > >> > Downloading: > >> > https://www.mycomp.com/maven2/repository/public/org/apache/maven/ > >> > plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom > >> > 1K downloaded (maven-install-plugin-2.3.pom) [WARNING] *** > >> > CHECKSUM FAILED - Checksum failed on download: local = > >> > 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '' - > >> > IGNORING [INFO] > >> > - > >> > --- > >> > [ERROR] BUILD ERROR [INFO] > >> > - > >> > --- [INFO] Error building POM (may not be this project's > >> > POM). > >> > > >> > > >> > Project ID: org.apache.maven.plugins:maven-install-plugin > >> > POM > >> > Location: > >> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2. > >> > 3/maven-install-plugin-2.3.pom > >> > > >> > Reason: Not a v4.0.0 POM. for project > >> > org.apache.maven.plugins:maven-install-plugin > >> > at > >> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2. > >> > 3/maven-install-plugin-2.3.pom > >> > > >> > > >> > > >> > if using the -e version I get: > >> > > >> > [INFO] > >> > - > >> > --- [INFO] Trace > >> > org.apache.maven.lifecycle.LifecycleExecutionException: Unable to > >> > build project for plugin 'org.apache.maven.plugins:maven-install-plugin': > >> > Not a v4.0.0 POM. for project > >> > org.apache.maven.plugins:maven-install-plugin > >> > at > >> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2. > >> > 3/maven-install-plugin-2.3.pom > >> > at > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin( > >> > DefaultLifecycleExecutor.java:1557) > >> > at > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescri > >> > ptor(DefaultLifecycleExecutor.java:1851) > >> > at > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycle > >> > ForPackaging(DefaultLifecycleExecutor.java:1311) > >> > at > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLife > >> > cycleMappings(DefaultLifecycleExecutor.java:1275) > >> > > >> > > >> > > >> > Caused by: org.apache.maven.plugin.InvalidPluginException: Unable > >> > to build project for plugin > >> > 'org.apache.maven.plugins:maven-install-plugin': Not a v4.0.0 > >> > POM. for project org.apache.maven.plugins:maven-install-plugin > >> > at > >> > /data/colibria/repository/org/apache/maven/plugins/maven-install- > >> > plugin/2.3/maven-install-plugin-2.3.pom > >> > at > >> > org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVe > >> > rsion(DefaultPluginManager.java:293) > >> > at > >> > org.apache.maven.plugin.DefaultPluginM
RE: Maven XML Plugin & xml-resolver, using it and debugging it
try putting a catalogmanager.properties in same folder as your catalog.xml edit catalogs to match the path to the catalog.xml on your system. #CatalogManager.properties # 1 ..4 #This controls the screen printout as catalogs are processed. Keep it as low as you need until something goes wrong. verbosity=4 #If relative-catalogs is yes, relative catalogs in the catalogs property will be left relative; #otherwise they will be made absolute with respect to the base URI of this file. relative-catalogs=yes # Always use semicolons in this list. #This is the pointer to the catalog to use catalogs=/usr/local/share/sdl/xmlV4.4/catalog.xml # either public or system prefer=public #this option controls whether or not a new instance of the resolver is constructed for each parse. static-catalog=yes #toggle whether or not the resolver classes obey the # processing instruction. allow-oasis-xml-catalog-pi=yes catalog-class-name=com.sun.resolver.Resolver use.extensions=1 textinsert.extension=1 -Original Message- From: Nick Stolwijk [mailto:nick.stolw...@gmail.com] Sent: Tuesday, September 15, 2009 8:50 AM To: Maven Users List Subject: Re: Maven XML Plugin & xml-resolver, using it and debugging it I tried adding the rewrites to no avail. Trying something more with the xml-resolver and doctypes (It seems for doctypes xml-resolver needs public or system identifier and not the url) # java -cp /home/nick/.m2/repository/xml-resolver/xml-resolver/1.2/xml-resolver-1.2.jar org.apache.xml.resolver.apps.resolver -d 2 -c catalog.xml -p "-//W3C//DTD XHTML1.0 Strict//EN" doctype Cannot find CatalogManager.properties Loading catalog: ./xcatalog Loading catalog: catalog.xml Resolve DOCTYPE (name, publicid, systemid): public id: -//W3C//DTD XHTML 1.0 Strict//EN Result: file:/home/nick/projects/example/src/main/xslt/catalog/xhtml1-strict.dtd It should find the dtd file based on the doctype and my catalog. So it seems my configuration of the Maven XML plugin is wrong (Or that the plugin is broken, but that is just a last resort) My current configuration: org.codehaus.mojo xml-maven-plugin 1.0-beta-3 transform src/main/xslt/catalog/catalog.xml src/main/xslt/example src/main/xslt/printversion.xsl Any more tips? With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Tue, Sep 15, 2009 at 5:23 PM, Sean Hennessy wrote: > in your catalog.xml I don't see where you specify rewrite? > > > > > > uriStartString="http://docbook.org/xml/4.2/"; > rewritePrefix="file:///c:/usr/local/share/sdl/xmlV4.2/" /> > systemIdStartString="http://docbook.org/xml/4.2/"; > rewritePrefix="file:///c:/usr/local/share/sdl/xmlV4.2/" /> > [snip] -Original Message- > From: Nick Stolwijk [mailto:nick.stolw...@gmail.com] > Sent: Tuesday, September 15, 2009 7:06 AM > To: Maven Users List > Subject: Maven XML Plugin & xml-resolver, using it and debugging it > > Hi, > > I am trying to use the Maven XML Plugin to transform an xhml file to another > xhtml file with help of an xslt file. I've got my xslt file setup and the > plugin using it. > > However, XHTML files uses a Doctype like: > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> > > When I run the transformation, I get the following error: > > Server returned HTTP response code: 503 for URL: > http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd > > I have read the w3 policy on this files and understand they don't serve them > to applications. Applications should use a catalog file and provide the dtd's > themself. > > I've tried to supply a catalog file to the XML plugin, according to the > documentation, which points to the dtd's, which are also on my system. > > > V1.0//EN" > > "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd";> > > prefer="public" xml:base="file:///home/nick/projects/example-project"> > > uri="/src/main/xslt/catalog/xhtml1-strict.dtd" /> > http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"; > uri="/src/main/xslt/catalog/xhtml1-strict.dtd"/> > > > I've tried this with multiple xml:base and or uri parts, but it still
RE: Maven XML Plugin & xml-resolver, using it and debugging it
in your catalog.xml I don't see where you specify rewrite? http://docbook.org/xml/4.2/"; rewritePrefix="file:///c:/usr/local/share/sdl/xmlV4.2/" /> http://docbook.org/xml/4.2/"; rewritePrefix="file:///c:/usr/local/share/sdl/xmlV4.2/" /> [snip] -Original Message- From: Nick Stolwijk [mailto:nick.stolw...@gmail.com] Sent: Tuesday, September 15, 2009 7:06 AM To: Maven Users List Subject: Maven XML Plugin & xml-resolver, using it and debugging it Hi, I am trying to use the Maven XML Plugin to transform an xhml file to another xhtml file with help of an xslt file. I've got my xslt file setup and the plugin using it. However, XHTML files uses a Doctype like: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> When I run the transformation, I get the following error: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd I have read the w3 policy on this files and understand they don't serve them to applications. Applications should use a catalog file and provide the dtd's themself. I've tried to supply a catalog file to the XML plugin, according to the documentation, which points to the dtd's, which are also on my system. http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd";> http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"; uri="/src/main/xslt/catalog/xhtml1-strict.dtd"/> I've tried this with multiple xml:base and or uri parts, but it still keeps throwing the error. I've read about the system properties which should be read by the xml resolver to debug this. [1] It does not seem to give any more output than just the error. Is there some way to debug the xml-resolver or to just get the thing to work? [1] http://xml.apache.org/commons/components/apidocs/resolver/index.html With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl - 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: Properties: backslashes in pathname on Windows
ant's ${file.separator} ??
-Original Message-
From: stug23 [mailto:pat.poden...@gmail.com]
Sent: Thursday, April 23, 2009 8:56 PM
To: users@maven.apache.org
Subject: Properties: backslashes in pathname on Windows
Is there a way in Maven 2.0.9 to end up with forward slashes in a
file/directory pathname on the Windows platform when filtering a property such
as ${project.parent.basedir}?
I need to supply a file URL for a Hibernate URL specified in a persistence.xml
configuraton file. The following property statement from a persistence.xml file
gets filtered as a resource file from src/test/resources into the test-classes
directory under target.
However on Windows the pathname ends up including backslashes which don't play
well with Hibernate. The JPA hibernate entity manager cannot resolve a URL with
backslashes in it.
The XML element in questions looks more or less like this:
Suggestions on how to accomplish this would be appreciated.
TIA!
--
View this message in context:
http://www.nabble.com/Properties%3A-backslashes-in-pathname-on-Windows-tp23209361p23209361.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Possible problem when multiple developers depend on SNAPSHOT versions
"What can be done to prevent Bob's problem?" Evidence to the contrary that Bob and Alice are working independently is they share development on single artifact Foo. Ensure Alice and Bob communicate daily on the development plan, schedule and status. Unless they are married..in which case you're stuffed ;-) -Original Message- From: Trevor Harmon [mailto:tre...@vocaro.com] Sent: Wednesday, March 25, 2009 12:11 PM To: Maven Users List Subject: Possible problem when multiple developers depend on SNAPSHOT versions Consider this scenario: Alice and Bob are working independently on two different applications, AppA and AppB. Both applications depend on an in-house shared library, Foo, that Alice and Bob are working on together. They have both checked out Foo's trunk and are regularly committing changes to it. Because Foo is undergoing heavy development, AppA and AppB depend on Foo 2.1-SNAPSHOT, but now Foo is looking pretty stable, and Alice's AppA needs some of the features scheduled for Foo 2.2, so she decides to perform a release of Foo 2.1 and does the usual release procedure: 1) Changes Foo's version from 2.1-SNAPSHOT to 2.1 and checks it into the trunk 2) Deploys Foo 2.1 to the company's internal repository 3) Tags the Foo trunk as the 2.1 release branch 4) Changes Foo's version from 2.1 to 2.2-SNAPSHOT and checks it into the trunk 5) Changes AppA's dependency to point to Foo 2.2-SNAPSHOT But what about Bob? He's still working with Foo 2.1-SNAPSHOT for his AppB. If he updates his working copy of Foo's source code, any changes he makes to Foo will be built as a 2.2-SNAPSHOT release, since Foo's trunk is now 2.2-SNAPSHOT. This is a major problem because his AppB has a dependency on 2.1-SNAPSHOT, so the next time he tests AppB, it will pick up the old Foo 2.1-SNAPSHOT, ignoring any changes Bob makes in Foo. He will probably waste a lot of time debugging, at least until he happens to notice that Foo's version has changed. What can be done to prevent Bob's problem? Trevor - 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: .Net unsafe compilation option in maven-net-plugin
By safe and unsafe you mean a mixed model project using managed (C# assemblies) and unmanaged (C++ .dll)? This would imply separate poms for the mananged and unmanaged components using different profiles to handle the specific compiler command line options. Perhaps the msvc compiler is smart enough to differentiate .c++ vs .cpp on it's own? Regards, Sean -Original Message- From: SRINIVASA RAO [mailto:srinivasv_amb...@yahoo.com] Sent: Friday, March 06, 2009 4:18 AM To: users@maven.apache.org Subject: .Net unsafe compilation option in maven-net-plugin Hi, i am using maven net plugin for .Net code compilation. But , My .Net code contains the some unsafe code. could you please let me know, how complie the unsafe .Net code. Regards, Sam - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Problems with maven-kogo-plugin
transcription error perhaps? maven-kodo vs maven-kogo -Original Message- From: maven_noob [mailto:kristianfra...@gmail.com] Sent: Tuesday, February 10, 2009 7:33 AM To: users@maven.apache.org Subject: Problems with maven-kogo-plugin I'Hi there - I'm trying to get this plug in to work when installing one of my projects. This is the message I am getting when trying to do an mvn install: [INFO]task-segment: [install] [INFO] [INFO] artifact org.apache.maven.plugins:maven-eclipse-plugin: checking for updates from central [INFO] [ERROR] FATAL ERROR [INFO] [INFO] The PluginDescriptor for the plugin Plugin [maven-plugins:maven-kodo-plugin] was not found. [INFO] [INFO] Trace java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [maven-plugins:maven-kodo-plugin] was not found. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:325) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1238) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1004) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue Feb 10 09:25:37 CST 2009 The pom for my project contains the following: maven-plugins maven-kodo-plugin 3.1.2 compile enhance Any suggestions? Thanks! -- View this message in context: http://www.nabble.com/Problems-with-maven-kogo-plugin-tp21936149p21936149.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: [doxia-maven-plugin] How to get images from book's apt directory into site?
Hi Paul,
# try placing images relative to {basedir}/src/site/resources
# maven-antrun-plugin pre-site
# is good time to render other formats like docbook
# and copy images from your source tree to appropriate resources folder.
# for example;
# in {basedir}/src/site/apt/index.apt using the following image reference.
[ 1.doc/images/labbenchmap.jpg ] Lab Office 65 layout
# and the corresponding image located here.
{basedir}/src/site/resources/1.doc/images/labbenchmap.jpg
# after call to mvn -X -e site -o >mvn_site.log
# results are found {basedir}/target/site/1.doc/images/
given your {basedir}/src/books/user-guide/apt
I would think {basedir}/src/resources/books/user-guide/myImage.png likely place.
Regards,
Sean
-Original Message-
From: Paul Spencer [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2008 2:29 PM
To: Maven Users List
Subject: [doxia-maven-plugin] How to get images from book's apt directory into
site?
I am working with doxia-maven-plugin 1.0-alpha-11. One of my apt files
contains a figure, as defined by [myImage.png]. Per the
documentation[1], the image file for the figure is in the same directory
as the apt file, src/books/user-guide/apt. "mvn site" generated the
pages for the book, including the tag to
include the image. Although I have followed the "Configuring Maven
Doxia Plug-in" example [2] with the exception if setting the plugin
version to 1.0-alpha-11 and using only the xdoc format, the image file
is not in the same directory as the generated html. Suggestions?
Paul Spencer
[1] http://maven.apache.org/doxia/references/apt-format.html
[2] http://maven.apache.org/doxia/book/index.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven/OS X Development Question
Hi John, I did not see if the expected "java -version" matches that of your mvn -x output shared. I recall a link operation ( ln -s ) was required on Mac volume to get newer JDK hooked up correctly. Sean -Original Message- From: John [mailto:[EMAIL PROTECTED] Sent: Friday, September 05, 2008 10:22 AM To: Maven Users List Subject: Re: Maven/OS X Development Question Hi Scott, Thanks for the reply. I am able to do "regular" java development (Elipse, IntelliJ, ant, JBoss, Tomcat, Geronimo, webapps, ears, jar files etc). However, when I use *any* version of Maven and perform a "mvn install", I get an error. I've documented it here (http://discussions.apple.com/thread.jspa?threadID=1695479&tstart=15) and have spent considerable (far too much) time on it already. I've even updated the Java version from the Apple site. About the only other thing I can think to do, besides throwing my computer from the top of the highest building I can find, is to reinstall OS X. Thanks again, John Scott Ryan wrote: > I have exactly that configuration and it has been working fine for > over a year. You might try to see if Appfuse works on it. Appfuse > has an Archetype that will build a totally new self contained running > application for you. Anything I can do to help let me know. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Too many open files during surefire test
Is the XSD file well formed? Do you receive any complaint from xml editor (eg:XMLSpy) opening the XSD file? What are the chances the XSD file have a circular reference definition? -Original Message- From: Kathryn Huxtable [mailto:[EMAIL PROTECTED] Sent: Saturday, June 21, 2008 1:15 AM To: Maven Users List Subject: Re: Too many open files during surefire test Getting closer. If I do mvn surefire:test Everything works fine. If I do mvn test I get the "too many open files" message. I get this even if I set forkMode to "never". I still think this is a spurious bug in Maven and not in the code I'm working on, simply because the error happens on the first file it tries to open, which is an XSD file being used by a SAX parser in commons-digester. This isn't rocket science. -K, slogging on and unable to sleep. I'm in GMT-0600. On Jun 20, 2008, at 3:33 PM, Kathryn Huxtable wrote: > Thanks. I'm running on Mac OS X 10.5.3. (The latest.) The ulimit for > files is unlimited. > > I have a Windows system and an Ubuntu system in the house. (I work > from home.) I'll try it on those platforms, too. > > I'm inclined to think that the error is bogus, simply because the test > has barely started. > > I'll take your advice on debugging it, though. > > -K > > On Jun 20, 2008, at 3:19 PM, Jon Seymour wrote: > >> The way I would debug this is start maven in debug mode (search for >> -Xdebug in the mvn launcher and add the relevant options to >> MAVEN_OPTS). Fire up your remote java debugger (e.g. in Eclipse or >> equivalent) then set a break point on the exception. You also need to >> set the forking option to never in your pom's surefire plugin >> configuration so that the tests run in the main maven process >> otherwise the breakpoint won't fire. >> >> If you are running on a unix that has lsof installed, once the >> breakpoint fires and while still paused on the breakpoint, fire up >> lsof to work out which files are being held open by the mvn Java >> process. If you don't have lsof, then at least you might get some >> insight into what files are the issue. >> >> Also, consider upping the ulimit setting for max open files [ if it >> is particularly low ]. >> >> jon. >> >> On Sat, Jun 21, 2008 at 6:10 AM, Kathryn Huxtable >> <[EMAIL PROTECTED]> wrote: >>> Nope, that's not it. I reduced it down to one test and it still >>> fails and it fails in setUp. -K >>> >>> On Jun 20, 2008, at 3:03 PM, Kathryn Huxtable wrote: >>> I'll take a look. It's not my code, or it would have been in maven to begin with. -K On Jun 20, 2008, at 12:58 PM, Jon Seymour wrote: > Haven't seen the error myself, but I suspect the problem you are > seeing is caused by a resource leak in your base code or your > tests. The reason you are seeing it in surefire and not in > testrunner is that > surefire creates a new class loader for every test which means > that > each test will be getting its own copy of the leaked resources, > thereby exhausting the underlying pool of OS resources faster. > > I'd be inclined to check that you are being hygenic with respect > to the closure of IO streams, especially on exception paths. > > Regards, > > jon seymour. > > On Fri, Jun 20, 2008 at 8:01 PM, Kathryn Huxtable > <[EMAIL PROTECTED]> wrote: >> >> I should have added that I'm running Maven 2.0.9 and >> maven-surefire-plugin 2.4.3. I'm supplying the argLine of >> -Xmx300M and I'm specifying a resource >> directory as an additional class path element. If I don't >> specify the >> memory >> I get out of memory errors. Specifying more doesn't help. >> >> -K >> >> On Jun 20, 2008, at 4:51 AM, Kathryn Huxtable wrote: >> >>> I'm converting a project from ant to maven and I'm getting a >>> "Too many open files" error during testing when it tries to open >>> some config >>> files in >>> a SAX parser. >>> >>> I don't get this error when using the TestRunner class from the >>> command line. >>> >>> I don't think the specific file is relevant, and I don't think >>> it's opening that many files... >>> >>> Any ideas? Has anyone seen this before? >>> >>> -K >>> >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >> >> >> - >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- > --- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -
RE: Can't pass "-Denv=dev" to scm:bootstrap goal
Is this a good time to bring up a potential name conflict between maven
convention and ant's use of 'env'?
eg:
provides all environment variables as Ant properties prefixed by "env."
-Original Message-
From: nicolas.duminil [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2008 7:59 AM
To: users@maven.apache.org
Subject: Can't pass "-Denv=dev" to scm:bootstrap goal
Greetings,
In a POM, I'm displaying the value of the "env" variable:
.
...
org.apache.maven.plugins
maven-antrun-plugin
verify
.
...
When running: "mvn -Denv=dev", the displayed line is "env: dev" as expected.
But if I run it: "mvn -Denv=dev scm:bootstrap -DconnectionUrl=... -Dgoals=...",
the display is "env: ${env}". As if the "-Denv=dev" hasn't given on the command
line. Of course, I tried also: "mvn scm:bootstrap -Denv=dev -DconnectionUrl=...
-Dgoals=..." but the result is the same.
Please help !
Many thanks in advance.
Nicolas
--
View this message in context:
http://www.nabble.com/Can%27t-pass-%22-Denv%3Ddev%22-to-scm%3Abootstrap-goal-tp17912903p17912903.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven @ Silicon Valley Web Developer Java User Group
Wish I could..however I'm willing to chip in ten dollars to help cover the cost of putting it on video that we might have access after the fact. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2008 4:53 PM To: Maven Users List Subject: Maven @ Silicon Valley Web Developer Java User Group Hi, For any Maven users who are interested in Eclipse IDE integration and Maven repository managers I will be speaking at the Silicon Valley Web Developer Java User Group on June 17th at Google in Mountain View. I will be speaking extensively on Nexus and m2eclipse and doing demos of both. The details are here: http://sv-web-jug-6.eventbrite.com/ Hope to see you there! Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- A man enjoys his work when he understands the whole and when he is responsible for the quality of the whole -- Christopher Alexander, A Pattern Language - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: need help in ant's javadoc task (from maven)
I have provided sample segments from a working pom.xml and build.xml for your
reference. One instruments ant echoproperties to help diagnose/debug the
classpath and other properties passed along from maven.
Sorry there is a limit to amount of time can spend on wht wrong.
Sean
-Original Message-
From: Niranjan Deshpande [mailto:[EMAIL PROTECTED]
Sent: Friday, June 06, 2008 3:35 PM
To: Maven Users List
Subject: Re: need help in ant's javadoc task (from maven)
so whts wrong in my case?
On Fri, Jun 6, 2008 at 7:31 PM, Sean Hennessy <[EMAIL PROTECTED]>
wrote:
> of course..echoproperties adds dependency..to another ant component.
> here is segment of my ugly pom.xml [snip]
>
>
>maven-antrun-plugin
>
>
>pre-site
>
>
>
>
>
>
>
> pattern="d-MMM-">
>
>pom.xml: timestamp ${TODAY_UK}
> name="mvndepClasspath" />
> antfile="${basedir}/src/4.bin/build.xml">
>
> name="project.debug">
>
>
>
>
>
>
> run
>
>
>
>
>
>org.apache.maven
>maven-artifact-ant
>2.0.4
>
>
>ant
>ant
>1.6.5
>
>
>ant-contrib
>cpptasks
>1.0b3
>
>
>ant-contrib
>ant-contrib
>1.0b2
>
>
>ant
>optional
>1.5.4
>
>
>ant
>ant-nodeps
>1.6.5
>
>
>
>
> [snip]
>
> in build.xml
> resource="org/apache/maven/artifact/ant/antlib.xml">
>
>
> -Original Message-
> From: Niranjan Deshpande [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 06, 2008 9:02 AM
> To: Maven Users List; [EMAIL PROTECTED]
> Subject: Re: need help in ant's javadoc task (from maven)
>
>
> I got this when I ran your debug script. Error executing ant tasks
>
>
> __
> ___
>
> Embedded error: The following error occurred while executing this
> line:
> /home/apli/APPWeb/src/main/build/generate/generate-appcodes.xml:37:
>
> Could not create task or type of type: echoproperties.
>
> Ant could not find the task or a class this task relies upon.
>
> This is common and has a number of causes; the usual solutions are to
> read the manual pages then download and install needed JAR files, or
> fix the build file:
> - You have misspelt 'echoproperties'.
> Fix: check your spelling.
> - The task needs an external JAR file to execute
> and this is not found at the right place in the classpath.
> Fix: check the documentation for dependencies.
> Fix: declare the task.
> - The task is an Ant optional task and the JAR file and/or libraries
> implementing the functionality were not found at the time you
> yourself built your installation of Ant from the Ant sources.
> Fix: Look in the ANT_HOME/lib for the 'ant-' JAR corresponding to the
> task and make sure it contains more than merely a META-INF/MANIFEST.MF.
> If all it contains is the manifest, then rebuild Ant with the needed
> libraries present in ${ant.home}/lib/optional/ , or alternatively,
> download a pre-built release version from apache.org
> - The build file was written for a later version of Ant
> Fix: upgrade to at least the latest release version of Ant
> - The task is not an Ant core or optional task
> and needs to be declared using .
> - You are attempting to use a task defined using
> or but have spelt wrong or not
> defined it at the point of use
>
> Remember that for JAR files to be visible to Ant tasks implemented in
> ANT_HOME/lib, the files must be in the same directory or on the
> classpath
>
> Please neither file bug reports on this problem, nor email the Ant
> mailing lists, until all of these causes have been explored, as this
> is not an Ant bug.
>
>
> __
> ___
>
> my xml file is in
RE: need help in ant's javadoc task (from maven)
of course..echoproperties adds dependency..to another ant component.
here is segment of my ugly pom.xml
[snip]
maven-antrun-plugin
pre-site
pom.xml: timestamp ${TODAY_UK}
run
org.apache.maven
maven-artifact-ant
2.0.4
ant
ant
1.6.5
ant-contrib
cpptasks
1.0b3
ant-contrib
ant-contrib
1.0b2
ant
optional
1.5.4
ant
ant-nodeps
1.6.5
[snip]
in build.xml
-Original Message-
From: Niranjan Deshpande [mailto:[EMAIL PROTECTED]
Sent: Friday, June 06, 2008 9:02 AM
To: Maven Users List; [EMAIL PROTECTED]
Subject: Re: need help in ant's javadoc task (from maven)
I got this when I ran your debug script. Error executing ant tasks
_
Embedded error: The following error occurred while executing this line:
/home/apli/APPWeb/src/main/build/generate/generate-appcodes.xml:37:
Could not create task or type of type: echoproperties.
Ant could not find the task or a class this task relies upon.
This is common and has a number of causes; the usual
solutions are to read the manual pages then download and install needed JAR
files, or fix the build file:
- You have misspelt 'echoproperties'.
Fix: check your spelling.
- The task needs an external JAR file to execute
and this is not found at the right place in the classpath.
Fix: check the documentation for dependencies.
Fix: declare the task.
- The task is an Ant optional task and the JAR file and/or libraries
implementing the functionality were not found at the time you
yourself built your installation of Ant from the Ant sources.
Fix: Look in the ANT_HOME/lib for the 'ant-' JAR corresponding to the
task and make sure it contains more than merely a META-INF/MANIFEST.MF.
If all it contains is the manifest, then rebuild Ant with the needed
libraries present in ${ant.home}/lib/optional/ , or alternatively,
download a pre-built release version from apache.org
- The build file was written for a later version of Ant
Fix: upgrade to at least the latest release version of Ant
- The task is not an Ant core or optional task
and needs to be declared using .
- You are attempting to use a task defined using
or but have spelt wrong or not
defined it at the point of use
Remember that for JAR files to be visible to Ant tasks implemented in
ANT_HOME/lib, the files must be in the same directory or on the classpath
Please neither file bug reports on this problem, nor email the Ant mailing
lists, until all of these causes have been explored, as this is not an Ant bug.
_
my xml file is in src/main/build/generate folder
and the dependency jars are in folder src/main/build/lib and
src/main/webapp/WEB-INF/lib I am using the to point
to these jars and and the tools.classpath is used by the ant's doclet task fpr
the "path" attribute.
What might be wrong?
On 6/6/08, Sean Hennessy <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> failonerror="false" />
>
>
>
>
>
>
>
>
> -Original Message-
> From: Niranjan Deshpande [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 06, 2008 5:54 AM
> To: [EMAIL PROTECTED]; Maven Users List
> Subject: need help in ant's javadoc task (from maven)
>
>
> I am trying to generate a .properties file using javadocs in a java
> source file, and i am using ant's task to do this.
>
> but i am getting this error when i run the antrun plugin
>
> generate.appcodes:
> [javadoc] Generating Javadoc
> [javadoc] Javadoc execution
> [javadoc] javadoc: Cannot find doclet class
> com.company.app.util.doclet.AppCodesDoclet
> [javadoc] 1 error
>
> Please help. Also can anyone tell me what the and
> elements are for? How are the paths relative to?
>
> My ant build file is:
>
>
>
>
>
>
>
>
&g
RE: need help in ant's javadoc task (from maven)
-Original Message- From: Niranjan Deshpande [mailto:[EMAIL PROTECTED] Sent: Friday, June 06, 2008 5:54 AM To: [EMAIL PROTECTED]; Maven Users List Subject: need help in ant's javadoc task (from maven) I am trying to generate a .properties file using javadocs in a java source file, and i am using ant's task to do this. but i am getting this error when i run the antrun plugin generate.appcodes: [javadoc] Generating Javadoc [javadoc] Javadoc execution [javadoc] javadoc: Cannot find doclet class com.company.app.util.doclet.AppCodesDoclet [javadoc] 1 error Please help. Also can anyone tell me what the and elements are for? How are the paths relative to? My ant build file is: -- Regards, Niranjan Deshpande "Shut yourself from the world and create the reality you want" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Running maven-compiler-plugin and maven-jaxws-plugin with different configurations in different phases
Perhaps one convention being the client bindings from another service could be resolved by a common IService class that each client Node would derive from and be dependent? Thereby decoupling the maven compile time binding to a generic class? >"Unless you mean that compilation of a webservice class requires client >bindings from >another service which is not yet built since it requires the >client bindings you are >about to build - that would be a painful circular >dep. But I guess such a situation >cannot be solved by "conventional" means >anyhow..." -Original Message- From: Jan Fredrik Wedén [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 21, 2008 11:25 AM To: Maven Users List Subject: Re: Running maven-compiler-plugin and maven-jaxws-plugin with different configurations in different phases Hmm, I'm not very familiar with jaxws so maybe I don't understand the full picture here. It just seems that if a class in one package can be compiled and used when generating wsdl and client bidnings without reference to other packages in the module, it can also be used for the same steps in module by itself. Unless you mean that compilation of a webservice class requires client bindings from another service which is not yet built since it requires the client bindings you are about to build - that would be a painful circular dep. But I guess such a situation cannot be solved by "conventional" means anyhow... On Wed, May 21, 2008 at 7:03 PM, Clint Gilbert <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Jan, thank you very much for your suggestion. > > That was almost the first thing I tried. The problem is that my web > service instances (I call them Nodes - they're components of a > distributed DB system) need to talk to each other. > > A Node needs to be compiled to generate the client bindings, and a > Node needs to invoke the bindings to talk to other Nodes. There's > always a circular dependency. I tried to > get around this by abstracting the process of talking to a node in order to > hide the JAXWS > client bindings from the nodes that use them. That let me attempt the > two-pass > compilation hack, but can't get around the circular dependency. > > I think I'm going to bootstrap my module by checking in the generated > code and artifacts. > > Just for reference, does anyone know for sure if you can give > different configs for different s of maven-compiler-plugin? > > Jan Fredrik Wedén wrote: > | Hi, > | > | Could you not split this into two modules where your step 4 resides > | in a module which dependes on another module containing the results > | from 1, 2 and 3? Seems like the most correct Maven-way if you are > | allowed to split your codebase to accomplish this. > | > | On Wed, May 21, 2008 at 2:48 AM, Clint Gilbert > | <[EMAIL PROTECTED]> wrote: Hello everyone, > | > | First of all, I cannot overstate the beneficial effect that Maven > | has had > on > | the > | development process at my organization. To the devs: thanks for the > | great tool! > | > | I have a pom that specifies two executions of the compiler plugin, > | with different phases specified and different configs, but they're > | not both running. (See pom excerpt below.) > | Is that expected? Can I configure multiple executions of the compiler > | plugin with > | different configurations? It seems like no - [1], [2], [3] - but I hope > | someone has an > | definitive answer. > | > | Here's some background on my problem, which I admit is fairly > | obscure. Basically, what I need to do is: > | > | 1 Compile class A in package org.myorg, which is annotated with > @WebService > | > | 2 Run JAXWS's wsgen (via maven-jaxws-plugin) to make a WSDL from the > | compiled A.class > | > | 3 Run JAXWS's wsimport (via maven-jaxws-plugin) to make client-side > bindings > | from the > | just-generated WSDL > | > | 4 Compile non-generated classes that reference the just-generated > | client bindings. These live in separate sub-packages - org.myorg.x, > | org.myorg.y, etc - and would have failed if > | compiled during step 1 because they reference code generated in step 3. > | > | I've included (what I hope are) the relevant sections of my pom > | below. > | > | PS: Do I need to do things this way? Unfortunately, I think so. > | Class org.myorg.A is a web service that needs to invoke other > | org.myorg.A web services arranged > in > | a tree or mesh > | topology. I've tried to break out the bindings, the SEI (A), and > | the classes that abstract the connection between As using the client > | bindings into submodules, but I've > | only managed to introduce circular dependencies. > | > | In the past, I've dealt with this sort of chicken-and-egg problem by > | generating WSDLs and code and then checking them into source > | control. This feels bad, and > makes > | updates if the > | interface of the SEI changes a hassle. I'd much rather define a > | simple > SEI > | annotated with > | @W
RE: Build Error in Maven
Does windows OS differentiate Internet Exploder firewall permissions, allow access to http://repo1.maven.org, however maven application firewall permission as separate? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2008 11:30 AM To: Maven Users List Subject: Re: Build Error in Maven How do you know you're not using a proxy? It is pretty simple to set up a transparent (aka intercepting) web proxy like squid. Perhaps try TraceTCP and make sure there's no proxy: http://tracetcp.sourceforge.net/usage_proxy.html There is no good reason why this should not work if you do not have a web proxy. As I said before, these kinds of issues are nearly impossible for someone outside of your network to help you debug/resolve, so you're going to have to work with local network admin resources to solve it. Wayne On 3/21/08, maluri <[EMAIL PROTECTED]> wrote: > > Yes. I am able to access http://repo1.maven.org from my desktop > without a proxy. > > > > Brian E Fox wrote: > > > > Go back to my first question: > > Are you able to access http://repo1.maven.org from your desk without > > a proxy? > > > > > > -Original Message- > > From: maluri [mailto:[EMAIL PROTECTED] > > Sent: Friday, March 21, 2008 11:41 AM > > To: users@maven.apache.org > > Subject: RE: Build Error in Maven > > > > > > Hi Brian, > > I deleted the repository folder under .m2\. But still I am facing > > the same problem. 2.0.9 is not showing under maven downloades in > > Apache.org site. I > > could only work with 2.0.8. I have uninstalled and installed the maven > > several times by downloading from different mirros in apache. Still > > doesn't > > work. It only gives me version. None of the commands working. For > > every > > command I try I get the below build error. > > > > Any suggestions? > > > > Thanks > > Madhu > > > > > > > > Brian E Fox wrote: > >> > >> Are you able to access http://repo1.maven.org from your desk > >> without a proxy? Try clearing your repository by deleting > >> $HOME/.m2/repository (the logs below don't show it even attempting > >> to download, which could mean bad metadata...this is fixed in > >> 2.0.9) > >> > >> -Original Message- > >> From: maluri [mailto:[EMAIL PROTECTED] > >> Sent: Thursday, March 20, 2008 7:51 PM > >> To: users@maven.apache.org > >> Subject: Build Error in Maven > >> > >> > >> When I try to run any command other than mvn -v I am getting the > >> below error. I have installed the maven 2.0.8 properly and > >> everything looks good. Please > >> let me know the solution. > >> > >> > >> H:\>mvn help:describe -Dplugin=help > >> [INFO] Scanning for projects... > >> [INFO] Searching repository for plugin with prefix: 'help'. [INFO] > >> org.apache.maven.plugins: checking for updates from central > >> [WARNING] repository metadata for: 'org.apache.maven.plugins' could > > not > >> be > >> retri > >> eved 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-help-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: 21 seconds > >> [INFO] Finished at: Thu Mar 20 15:20:30 PDT 2008 > >> [INFO] Final Memory: 1M/4M > >> [INFO] > >> > > > > > >> > >> H:\>mvn help:describe -Dplugin=compiler -Dmojo=compile -Dfull > >> [INFO] Scanning for projects... [INFO] Searching repository for > >> plugin with prefix: 'help'. [INFO] org.codehaus.mojo: checking for > >> updates from central [WARNING] repository metadata for: > >> 'org.codehaus.mojo' could not be retrieved fr > >> om 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-help-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: 21 seconds > >> [INFO] Finished at: Thu Mar 20 15:21:
RE: listing all the properties set via profiles
believe you may need to add the optional dependency for echoproperties. been using this version with success. ant optional 1.5.4 -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, February 28, 2008 11:26 AM To: Maven Users List Subject: RE: listing all the properties set via profiles Here's a snippet from the pom: propgen propgen maven-antrun-plugin org.apache.ant ant-nodeps 1.7.0 props process-resources run -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, February 28, 2008 2:05 PM To: Maven Users List Subject: RE: listing all the properties set via profiles It dawned on me that ant has an task, but with ant and ant-nodeps added as dependencies, it still gives the error: Could not create task or type of type: echoproperties. Ant could not find the task or a class this task relies upon. Is there something else that's necessary? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, February 28, 2008 1:27 PM To: users@maven.apache.org Subject: listing all the properties set via profiles Is there a plugin or configuration (or something) that echoes out a list of all the properties available when given a list of profiles? I wrote something long ago to do this, but I'm wondering if something more off-the-shelf may exist now. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Artifact problem on vista
complete command line you are using? similar problems in past were due missing mvn option -DarchetypeGroupId=org.apache.maven.archetypes log suggests it is trying to match GroupID of org.apache.maven.plugins instead of org.apache.maven.archetypes?? Sean -Original Message- From: Toby Hobson [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 20, 2007 3:00 PM To: Maven Users List Subject: Re: Artifact problem on vista Nope ... just a normal wifi router/firewall and my xp laptop works ok Toby - Original Message From: Wayne Fay <[EMAIL PROTECTED]> To: Maven Users List Sent: Tuesday, 20 November, 2007 10:52:55 PM Subject: Re: Artifact problem on vista Are you perhaps behind an Internet proxy of some kind? If so, you must configure things in settings.xml. This is documented on the site and/or Wiki. Wayne On 11/20/07, Toby Hobson <[EMAIL PROTECTED]> wrote: > ok good point Wayne! I've disabled the windows firewall and antivirus but > i'm still having no luck: > > C:\Users\toby\workspace>mvn -DgroupId=com.test -DartifactId=test -X -U > archetype > :create > + Error stacktraces are turned on. > Maven version: 2.0.7 > Java version: 1.6.0_03 > OS name: "windows vista" version: "6.0" arch: "x86" > [DEBUG] Building Maven user-level plugin registry from: > 'C:\Users\toby\.m2\plugi n-registry.xml' > [DEBUG] Building Maven global-level plugin registry from: 'c:\Program > Files\Java > \maven-2.0.7\bin\..\conf\plugin-registry.xml' > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins > [INFO] org.apache.maven.plugins: checking for updates from central > [DEBUG] repository metadata for: 'org.apache.maven.plugins' could not be > found o > n repository: central > [DEBUG] Loading plugin prefixes from group: org.codehaus.mojo [INFO] > org.codehaus.mojo: checking for updates from central [DEBUG] > repository metadata for: 'org.codehaus.mojo' could not be found on > repos > itory: central > [INFO] artifact org.apache.maven.plugins:maven-archetype-plugin: checking > for up > dates from central > [DEBUG] repository metadata for: 'artifact > org.apache.maven.plugins:maven-archet > ype-plugin' could not be found on repository: central > [DEBUG] maven-archetype-plugin: using locally installed snapshot > [DEBUG] Artifact not found - using stub model: Unable to determine the > latest ve > rsion > > org.apache.maven.plugins:maven-archetype-plugin:pom:LATEST > > > [DEBUG] Using defaults for missing POM > org.apache.maven.plugins:maven-archetype- > plugin:pom:LATEST > [DEBUG] maven-archetype-plugin: using locally installed snapshot > [DEBUG] Artifact not found - using stub model: Unable to determine the > release v > ersion > > org.apache.maven.plugins:maven-archetype-plugin:pom:RELEASE > > > [DEBUG] Using defaults for missing POM > org.apache.maven.plugins:maven-archetype- > plugin:pom:RELEASE > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exi > st or no valid version could be found > [INFO] > > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.m aven.plugins:maven-archetype-plugin' does not exist or > no valid version > could be > found > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa > ultLifecycleExecutor.java:1286) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor > (DefaultLifecycleExecutor.java:1522) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListBy > AggregationNeeds(DefaultLifecycleExecutor.java:386) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:138) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.version.PluginVersionNotFound
RE: Artifact problem on vista
Perhaps you might try adding -U option to command line and archetypeGroupId also..or simpler maven-archetype-site first? C:\Users\toby\workspace>mvn -U -e archetype:create -DgroupId=com.mycompany.app -DarchetypeGroupId=org.apache.maven.archetypes -DartifactId=my-webapp -DarchetypeArtifactId=maven-archetype-webapp -Original Message- From: Toby Hobson [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 20, 2007 6:40 AM To: users@maven.apache.org Subject: Artifact problem on vista Hi guys, I've recently installed Maven 2.0.7 together with jdk 1.6 on Windows Vista and I'm having quite a few problems. It seems maven is unable to download most of the artifacts I need, for example the following command doesn't work: C:\Users\toby\workspace>mvn -e archetype:create -DgroupId=com.mycompany.app -DartifactId=my-webapp -DarchetypeArtifactId=maven-archetype-webapp I get the following error: [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exi st or no valid version could be found [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.m aven.plugins:maven-archetype-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa ultLifecycleExecutor.java:1286) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor (DefaultLifecycleExecutor.java:1522) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListBy AggregationNeeds(DefaultLifecycleExecutor.java:386) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:138) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The p lugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no val id version could be found at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePl uginVersion(DefaultPluginVersionManager.java:228) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePl uginVersion(DefaultPluginVersionManager.java:90) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlug inManager.java:166) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa ultLifecycleExecutor.java:1257) ... 14 more [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Tue Nov 20 14:35:53 GMT 2007 [INFO] Final Memory: 1M/4M [INFO] I have installed maven in c:\program files\java\maven-2.0.7 I had no problems using maven with xp so i suspect the problem may be something to do with vista's more restrictive permissions. Has anyone else come across this problem? Thanks Toby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Question about native library path
Maven has promise for being a worthwhile tool and we all share the expectation that it will get better. I get from this thread that Wayne is frustrated with the available resources to target more feature development. Dave appears to be equially frustrated. Perhaps the Maven team would consider adding a vote your feature with donation component to the site. That way companies and individuals may participate in a positive way toward Maven even though they may not be able to manage the time at the contributor level? Best Regards, Sean -Original Message- From: Dave Feltenberger [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 06, 2007 7:28 AM To: Maven Users List Subject: Re: Question about native library path The reason the *user's* list exists is to discuss using Maven, not to lecture people about adding features that may or may not exist. If a person wants to find out if features exist, or has a question about usage, they should not be lectured about adding the features themselves. A simple, "I don't think this feature exists" suffices. I am -- and I'm sure the vast majority of others are -- quite aware that this is an open source project and I can contribute, but during the normal course of a work day my employer pays me to make software for them, not drain resources to modify open source projects that are designed to support our infrastructure. When I ask questions on OS project lists, I try to contribute by answering a question or two that I'm able to answer, as adding features to the projects is simply not something I'm able to rationalize to my employers. On Nov 2, 2007 4:22 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > Any time, Dave! Some people simply need a little nudge in the right > direction. > > It seems like a lot of people on this list either don't realize or > forget that Maven is Open Source Software. You're a developer, right?? > If you want a feature and it isn't obviously available, go write some > code!! Maven plugins are (generally) trivial to modify or even create > from scratch to deal with a particular issue. > > The only way that Maven gets any better is by the contributions of > people (like yourself) -- some in the core dev team and others who are > simply motivated users who want to get their work done. > > In the (short) amount of time we've spent discussing this issue, you > could have already written and tested your addition to the Eclipse > plugin, and you'd be on dealing with the next issue in your project. > > > Wayne > > On 11/2/07, Dave Feltenberger <[EMAIL PROTECTED]> wrote: > > Thank you for pointing out that if a feature doesn't exist I'm free > > to add the necessary features myself, Wayne. > > > > On Nov 2, 2007 2:16 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > Its possible this functionality is not currently available. Take a > > > look at the source code, add in your needed features, and > > > contribute it back for future inclusion in the next release of the > > > Eclipse plugin. > > > > > > Wayne > > > > > > > > > On 11/2/07, Dave Feltenberger <[EMAIL PROTECTED]> wrote: > > > > All, > > > > > > > > Does anybody know if it's possible (and if so, how) to add the > > > > native library location to a classpath entry? Specifically the > > > > Eclipse .project classpath attribute > > > > "org.eclipse.jdt.launching.CLASSPATH_ATTR_LIBRARY_PATH_ENTRY". > > > > I'd like to have some dlls in my library path without having to > > > > add additional JVM arguments everytime I create a launcher (and > > > > without having to specify it JVM-wide or something). The > > > > closest thing I could find in the project documentation was > > > > "classpathContainers", but that's not exactly it. Here's an > > > > example of what I'd want the end result to be: > > > > > > > > > > > path="M2_REPO/org/ecliplse/swt/swt/3.323/swt.jar"> > > > > > > > > > > > name="org.eclipse.jdt.launching.CLASSPATH_ATTR_LIBRARY_PATH_ENTRY" > > > > value="MySwtProject/target/swt-native-libs"/> > > > > > > > > > > > > > > > > And I can't figure out how to add the additional attributes > > > > without doing it manually in Eclipse everytime. > > > > > > > > Thanks. > > > > > > > > Dave > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > -- > > > --- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMA
RE: Filtering Site Documents With Periods in Property Names - Suspect Bug
Yes. I've seen this behavior in ant build.xml constructs as well so am
reluctant to point the finger at Maven.
My guess is somewhere in the works there is confusion as to whether one
is referring to a package.class or property.name even though the
definitions originate in a .properties file!
I've learned to use property_name convention.
Regards,
Sean
-Original Message-
From: Cam [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 17, 2007 7:35 AM
To: users@maven.apache.org
Subject: Filtering Site Documents With Periods in Property Names -
Suspect Bug
Hi ml,
I've been trying to get property filtering to work over the site
documents as specified in
http://maven.apache.org/plugins/maven-site-plugin/usage.html by
appending the '.vm' extension to the appropriate files. The problem is
that the property filtering doesn't seem to work when the property names
contain periods for breaking up the context words, for example:
The works:
${currentVersion}
This doesn't:
${current.version}
For some reason the default maven properties which are always available
DO work even if they have periods, for example this is resolved
correctly:
${project.version}
Seems like some strange behavior and it took me a while to nutt it out.
Anyone else seen this, is it a valid bug for the component?
Thanks,
Cam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Where to put documents
Hi Randal, Given command line mvn site and in the pom.xml there exists a pre-site phase to move/generate proj.mgmt artifacts.. maven-antrun-plugin pre-site we place proj. mgt. artifacts in src/site/resources/yourProjDocs they will find a home under target/site/yourProjDocs. having made the corresponding changes to site.xml yourProj ./yourProjDocs/images/yourProjLogo.jpg http://yourProj.com/ ./yourProjDocs/images/yourProjLogo2.jpg Regards, Sean -Original Message- From: Randall Fidler [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 09, 2007 9:47 AM To: users@maven.apache.org Subject: Where to put documents Hello, Looking at the standard Maven directory layout (http://maven.apache.org/guides/introduction/introduction-to-the-standar d-directory-layout.html) I'm curious if there's a place to incorporate non-source application documents, misc. flow diagrams for example. I would think that mapping them into /docs, as opposed to /src, would be fine but if Maven has some pre-defined place for it and subsequently that location feeds some plug-in or process, then I'd like to start out on the right foot. Thanks, Randall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven native plugin
To expand on this.. Given the following command line options defined for the compiler; -idirafterdir Add directory (dir) to the second include file search path (after -I). -Idirectory Specifies an additional directory to search for include files -Ldirectory Instruct linker to search directory for libraries one would modify the sample pom and adjust the start, middle and end options of the compiler and linker as required or suggested by output. Good luck, http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 com.mycompany.app my-app so 1.0-SNAPSHOT my-app http://maven.apache.org junit junit 3.8.1 test org.codehaus.mojo native-maven-plugin true generic icl -I"C:\Programme\Intel\Compiler\C++\9.1\IA32\Includ e" -shared -lxml2 -lz -lpthread -ldl -L"C:\Programme\Intel\Compiler\C++\9.1\IA32\Lib" /src/main/native *.cpp -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 6:48 AM To: Maven Users List Subject: Re: Maven native plugin take tout C:\Programme\Intel\Compiler\C++\9.1\IA32\Include *.h C:\Programme\Intel\Compiler\C++\9.1\IA32\Lib *.lib *.dll - Dont think we support compilation of .h file - Dont think the compliler can compile .dll files - Dont think we support *.lib, you must explicitely link it via LinkerStartOption using your linker specific arguments Best to take to present INCLUDE and LIB system environment variables prior to running mvn -D On 5/7/07, jBeuchat <[EMAIL PROTECTED]> wrote: > > > Thank you for your answer. > I have done what you told me to do, but still have an error. There is > something wrong, but i don't know what. > > > The dependencies? > The sources? > > or that? > generic > icl > > ?? > > THank you for your help! > > Here my "pom.xml" : > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > com.mycompany.app > my-app > so > 1.0-SNAPSHOT > my-app > http://maven.apache.org > > > junit > junit > 3.8.1 > test > > > > > > org.codehaus.mojo > native-maven-plugin > true > > > -shared -lxml2 -lz -lpthread > -ldl > > > > /src/main/native > > *.cpp > > > > > C:\Programme\Intel\Compiler\C++\9.1\IA32\Include > > *.h > > > > > C:\Programme\Intel\Compiler\C++\9.1\IA32\Lib > > *.lib > > > *.dll > > > > generic > icl > > > > > > > > Sean Hennessy wrote: > > > > > > It appears that an include path directive is missing on the command > line. > > Hunt through the Intel compiler and the native documentation > > http://mojo.codehaus.org/maven-native/native-maven-plugin/usage.html > > and find the section in the pom that allows one to specify include > files/paths > > for the compiler. > > It might be that you will experiment with the > > .. > > > > > > -- > View this message in context: > http://www.nabble.com/Maven-native-plugin-tf3639190s177.html#a10370684 > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven native plugin
It appears that an include path directive is missing on the command line. Hunt through the Intel compiler and the native documentation http://mojo.codehaus.org/maven-native/native-maven-plugin/usage.html and find the section in the pom that allows one to specify include files/paths for the compiler. It might be that you will experiment with the .. -Original Message- From: Beuchat José [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 24, 2007 7:53 AM To: users@maven.apache.org Subject: Maven native plugin Hello, I want to use the maven "native plugin" to compile C++ project. The compilator is ok, but I've problems with the libraries. Here the error message: D:\MavenTests\my-app>mvn package [INFO] Scanning for projects... [INFO] [INFO] Building my-app [INFO]task-segment: [package] [INFO] [INFO] [native:initialize] [INFO] [native:compile] [INFO] icl -ID:\MavenTests\my-app\src\main\native -o D:\MavenTests\my-app\target\test. obj -c D:\MavenTests\my-app\src\main\native\test.cpp Intel(R) C++ Compiler for 32-bit applications, Version 9.1Build 20060706Z Package ID: W_CC_C_9.1.028 Copyright (C) 1985-2006 Intel Corporation. All rights reserved. test.cpp D:\MavenTests\my-app\src\main\native\test.cpp(1): catastrophic error: could not open s ource file "iostream" #include ^ compilation aborted for D:\MavenTests\my-app\src\main\native\test.cpp (code 4) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing command line. Exit code:4 [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue Apr 24 16:51:47 CEST 2007 [INFO] Final Memory: 4M/9M [INFO] Could you help me? Or give me an example of the pom.xml file with specified libraries? Sincerely Beuchat José Informatiker ISS AG Allmendstrasse 11 CH - 2563 Port / Schweiz [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Proximity
-DrepositoryTd=proximity ?? transcription error?? -DrepositoryId=proximity -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, April 20, 2007 8:04 AM To: Maven Users List Subject: Re: Proximity I would assume the deploy failed because you haven't configured the authentication for your scp:// connection in settings.xml: http://maven.apache.org/settings.html#Servers Wayne On 4/20/07, Thorsten Heit <[EMAIL PROTECTED]> wrote: > Hi, > > > The problem is : when I try to deploy (upload) a jar using this > > command line : > > > > > > > > >mvn deploy:deploy-file -Dfile=./lib/asm-1.5.3.jar > > -DrepositoryTd=proximity \ > > > > > > -Durl=scp://localhost:8080/px-webapp-default-1.0.0-RC8/repository \ > > > > -DartifactId=asm -DgroupId=asm -Dversion=1.5.3 > > -Dpackaging=jar -e > > I don't use Proximity, but I wondered why you try to deploy the > artifact via SSH to your repository that is accessible via HTTP...? > Shouldn't the URL start with http://, webdav:// or similar? > > > HTH > > Thorsten > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: antrun: Could not create task or type of type: scriptdef
For your reference..
have some success using BUNDLED bsf and rhino to process Docbook
artifacts with ant..
see samples below
Regards,
Sean
maven-antrun-plugin
pre-site
pom.xml: timestamp ${TODAY_UK}
run
org.apache.maven
maven-artifact-ant
2.0.4
ant
ant
1.6.5
jtidy
jtidy
4aug2000r7-dev
ant-contrib
cpptasks
1.0b3
ant-contrib
ant-contrib
1.0b2
ant
optional
1.5.4
ant
ant-antlr
1.6.5
antlr
antlrall
2.7.4
ant
ant-nodeps
1.6.5
bsf
bsf
C:/usr/local/share/sdl/bsf-2_2/lib/bsf.jar
BUNDLED
system
js
js
C:/usr/local/share/sdl/rhino1_5R4_1/js.jar
BUNDLED
system
-Original Message-
From: Manos Batsis [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 04, 2007 7:27 AM
To: Maven Users List
Subject: antrun: Could not create task or type of type: scriptdef
Hello,
I'm trying to execute a scriptdef task through antrun as follows but get
the error in the subjectline. I have included BSF as a plugin dependency
and have tried to use inheritrefs/maven.plugin.classpath but no dice.
Err, heeelp?
Many thanks,
Manos
pom.xml fragment:
--
maven-antrun-plugin
antrun-test
test
run
bsf
bsf
2.3.0
build.xml fragment:
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven 2: antrun-plugin with ant-contrib tasks
Hi Jo, One example for your reference. I use for-each and
RE: maven version management in ant
FWIW
snippet of working maven pom.xml and ant build.xml
# pom.xml partial
[snip]
maven-antrun-plugin
pre-site
pom.xml: timestamp ${TODAY_UK}
run
[snip]
# build.xml
[snip]
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Monday, January 08, 2007 6:19 AM
To: Maven Users List
Subject: RE: maven version management in ant
Bump - I could really use some feed back here people, this has me
completely wedged...
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 3:56 PM
To: Maven Users List
Subject: RE: maven version management in ant
I made it a bit further:
The version is ${project.version}
${project.build.directory}
${project.name}
${project.dependencies}
Is the actual classpath used for compiling unavailable to ant as a
property?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 2:07 PM
To: Maven Users List
Subject: RE: maven version management in ant
New question, so I'm loading via a pom.xml file, how can I reference the
classpath (filled with dependencies)?
The version is ${project.version}
${project.build.directory}
???
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 3:49 PM
To: Maven Users List
Subject: RE: maven version management in ant
Sorry - I'm building with jdk 1.5.1 now and this is gone.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 1:03 PM
To: Maven Users List
Subject: RE: maven version management in ant
I'm trying this out with a VERY simple example (download one
dependency), but I'm getting this:
BUILD FAILED
java.lang.NoSuchMethodError
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1225)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut
or.java:40)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
--- Nested Exception ---
java.lang.NoSuchMethodError
at
org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
on.(ComponentConfigurationException.java:24)
at
org.codehaus.plexus.component.configurator.converters.basic.IntConverter
.fromString(IntConverter.java:46)
at
org.codehaus.plexus.component.configurator.converters.basic.AbstractBasi
cConverter.fromConfiguration(AbstractBasicConverter.java:61)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSett
er.configure(ComponentValueSetter.java:207)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
thFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:1
37)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
nfigureComponent(BasicComponentConfigurator.java:56)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:54)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:47)
at
org.codehaus.plexus.personality.plexus.lifecycle.phase.AutoConfigurePhas
e.execute(AutoConfigurePhase.java:39)
at
org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLif
ecycleHandler.java:101)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.startComp
onentLifecycle(AbstractComponentManager.java:105)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.createCom
ponentInstance(AbstractComponentManager.java:95)
at
org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.g
etComponent(ClassicSingletonComponentManager.java:92)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:331)
at
org.codehaus.plexus.DefaultPlexusContainer.initializeLoggerManager(Defau
ltPlexusContainer.java:1204)
at
org.codehaus.plexus.DefaultPlexusContainer.initi
RE: Maven2/Ubuntu archetype:create does not work
also check whitespace exists between command line parameters. "-DgroupId=mm.linux -DartifactId=testapp" -Original Message- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 03, 2007 12:43 PM To: Maven Users List Subject: Re: Maven2/Ubuntu archetype:create does not work Try deleting .m2/plugin-registry.xml file. That may work. Eric On 1/3/07, Marco Mistroni <[EMAIL PROTECTED]> wrote: > > hi all, > i m trying to createa small project using maven2 under ubuntu Linux > (5.10 > ) > > when i run this command > > [EMAIL PROTECTED]:~$ mvn -e archetype:create > -DgroupId=mm.linux-DartifactId=testapp > -DarchetypeArtifactId=maven-archetype-webapp > > i got following exception: > > [INFO] > -- > -- > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does > not > exist or no valid version could be found > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin ' > org.apache.maven.plugins:maven-archetype-plugin' does not exist or no > valid > version could be found > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin( > DefaultLifecycleExecutor.java:1281) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor( > DefaultLifecycleExecutor.java:1517) > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByA > ggregationNeeds > (DefaultLifecycleExecutor.java:381) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( > DefaultLifecycleExecutor.java:135) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java > :315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode( > Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: > The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist > or no valid version could be found > at > > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlu > ginVersion > (DefaultPluginVersionManager.java:225) > at > > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlu > ginVersion > (DefaultPluginVersionManager.java:87) > at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin( > DefaultPluginManager.java:158) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin( > DefaultLifecycleExecutor.java:1252) > ... 14 more > [INFO] --- > > > everything seems to be working fine if i create my own directory and > build myself a pom.xml > > can anyone tell me why? > > i have set MAVEN_HOME and JAVA_HOME environment variables do i > need to set an addtional one? > > thanks and regards > Marco > > -- Eric Redmond http://codehaus.org/~eredmond - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven2 under Linux
reference installation instuctions.
http://maven.apache.org/download.html#installation
typically there is a .bashrc file within your home directory
find it with "ls -la"
edit .bashrc and add
export PATH=/usr/local/maven-2.0.3/bin:$PATH
then test with "which mvn" will show where mvn lives..
Sean
-Original Message-
From: Marco Mistroni [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 2:07 PM
To: Maven Users List
Subject: Maven2 under Linux
hi all,
anyone is running maven2 on Linux platform? i have extracted the
tar.gz, have exported variables (MAVEN_HOME , path etc) and i run mvn
linux (ubuntu) keeps on saying me that it is an unknow command
and even if i move the the {MAVEN_HOME}\bin and run mvn i still get same
error
can anyone give me some help?
thanks in advance and regards
marco
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven site doctype validation
If your "smart editor" supports the use of com.sun.resolver.tools.CatalogResolver use rewriteURI and rewriteSystem mechanism to resolve the http DTD references to your local copies. [snip] http://maven.apache.org/dtd/"; rewritePrefix="file:///c:/usr/local/share/sdl/apache_dtd/" /> http://maven.apache.org/dtd/xdoc_1_0.dtd"; rewritePrefix="file:///c:/usr/local/share/sdl/apache_dtd/" /> [snip] -Original Message- From: jblack [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 13, 2006 1:21 PM To: users@maven.apache.org Subject: maven site doctype validation I want to add the DOCTYPE tag to our xdocs so we can use a smart editor to create these documents. But, I don't want the url to point to "http://maven.apache.org/dtd/xdoc_1_0.dtd";. There is a significant delay while maven site tries to validate these xdocs with the DOCTYPE tag. http://maven.apache.org/dtd/xdoc_1_0.dtd";> Can I host this dtd on an internal server and point the url to it's new location? Is this even the best solution? -- View this message in context: http://www.nabble.com/maven-site-doctype-validation-tf2267753.html#a6293 746 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to prevent from deploying the same version of artefact twice?
If one attempts to adopt the SCM recommendation / goal of separate development, unit test, integration, QA, and production environments it requires that developers be able to select ( through Maven profiles) any of the environments in order to reproduce and resolve behaviors (problems). The realization of such a controlled environment with Maven looks to be an exercise in the management of cvs tags, settings.xml and pom.xml files in order to keep released versions separate from SNAPSHOT versions. -Original Message- From: Artamonov, Juri [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 24, 2006 9:15 AM To: Maven Users List Subject: RE: How to prevent from deploying the same version of artefact twice? Also just small question. What is the reason and benefit to have two repositories if released versions can also be with SNAPSHOTS versions? -Original Message- From: Artamonov, Juri [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 24, 2006 7:12 PM To: Maven Users List Subject: RE: How to prevent from deploying the same version of artefact twice? Thank you very much, Fay, for your comprehensive answer. Best regards, Juri. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 24, 2006 7:01 PM To: Maven Users List Subject: Re: How to prevent from deploying the same version of artefact twice? Juri, he's suggesting the following approach: 1. Set up a Maven prerelease repository. Your developers etc will deploy artifacts here so they will need read/write access. 2. Set up a Maven release repo. Your developers will only use this repo to pull down dependencies, so they will need read-only access. You will appoint a particular person to be "release repo manager" who will copy artifacts from prerelease over to release repo as needed. Thus, your prerelease repo will be constantly overwritten with each deployment. But the release repo will be the master source of your artifacts. This requires that you do *not* add the pre-release repo in your poms as a repo -- only the release repo. You will only use the pre-release repo as a staging area for built artifacts. Wayne On 5/24/06, ben short <[EMAIL PROTECTED]> wrote: > Juri, > > Im sorry i dont understand what you are asking > > Ben > > On 5/24/06, Artamonov, Juri <[EMAIL PROTECTED]> wrote: > > Hi Ben, > > > > what do you mean under prelease and release sites? What is the site > > here? > > > > > > -Original Message- > > From: ben short [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, May 23, 2006 3:05 PM > > To: Maven Users List > > Subject: Re: How to prevent from deploying the same version of > > artefact twice? > > > > > > Ah i see what you are saying. > > > > Assuming that your developers are using svn ( or other source > > control > > ) in a correct manner, the release plugin should sort you out. > > > > http://maven.apache.org/plugins/maven-release-plugin/introduction.ht > > ml > > > > But i guess if you want to make doubley sure you could have a > > release site and a prerelease site. the developers release to the > > prerelease site and then someone vets the release and if ok moves it > > to the release site. > > > > > > On 5/23/06, Plygawko Dariusz (Centrala PZUSA) <[EMAIL PROTECTED]> > > wrote: > > > Yes, developing should be done using SNAPHOTs. But still from time > > > to time someone will have to deploy "stable" version (without > > > "-SNAPSHOT") and I after it would like to make this file completly > > > safe and "read-only"(automatically). But I don't know how to... > > > > > > -Original Message- > > > From: ben short [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, May 23, 2006 12:48 PM > > > To: Maven Users List > > > Subject: Re: How to prevent from deploying the same version of > > > artefact twice? > > > > > > > > > Kind of going against the whole idea of maven then. > > > > > > On 5/23/06, Plygawko Dariusz (Centrala PZUSA) <[EMAIL PROTECTED]> > > > wrote: > > > > Is it possible to workaround this problem if I don't want to use > > > > snapshots? :) > > > > > > > > > > > > -Original Message- > > > > From: Wim Deblauwe [mailto:[EMAIL PROTECTED] > > > > Sent: Tuesday, May 23, 2006 12:14 PM > > > > To: Maven Users List > > > > Subject: Re: How to prevent from deploying the same version of > > > > artefact twice? > > > > > > > > > > > > Use the release plugin, this will automatically change the > > > > version to the next SNAPSHOT version. > > > > > > > > 2006/5/23, dariusz.p <[EMAIL PROTECTED]>: > > > > > > > > > > > > > > > It's possible to overwrite the same version of an artefact > > > > > (when you forget to increment version in pom.xml after you > > > > > changed something in source code). How to prevent from it? I > > > > > use ftp server as internal repository (I > > can > > > > > switch to sth else if it's necessary). I would prefer to fix > > > > > it on > > the > > > > > server side instead of pachting deploy-plugin (there is alw
RE: broken build booby prize (was: how can I make a profile active when a property is NOT set?)
In a prior engagement to remain anonymous we used a rubber chicken until corporate feared potential harassment litigation. The suits took all the fun out of taking turns being the village idiot. -Original Message- From: Max Cooper [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 23, 2006 2:40 PM To: Maven Users List Subject: broken build booby prize (was: how can I make a profile active when a property is NOT set?) The last person to break the build does keep Mr. Hankey until someone else breaks the build. The downside of this practice is that there is a somewhat reduced penalty for consecutive offenses. :-) -Max John Casey wrote: > ah, I see. I like the booby prize...do they have to hold onto it until > the next guy breaks the build? ;-) > > -john > > On 5/23/06, Max Cooper <[EMAIL PROTECTED]> wrote: > >> >> A few things make this skipping the tests by default acceptable for >> our >> project: >> >> 1. Our tests more than double the run time of our build. Our tests >> take a relatively long time, so there is a fairly significant >> productivity penalty for running the tests every time a developer >> does a build. >> >> 2. Developers are encouraged to run the tests before a commit, or >> more often, as they see fit. >> >> 3. We have a continuous integration server running builds with tests >> every 3 minutes (it checks every 3 min, waits for a quiet period of 5 >> min). It emails us when the project status changes. If a test fails, >> we will know about it very quickly. We even have a "booby prize" >> (South Park My. Hankey doll) that will be delivered to your desk if >> you break the build. >> >> -Max >> >> John Casey wrote: >> > FWIW, I hope you have a *really* compelling reason to skip your >> > unit >> tests >> > by default. As long as we're writing things down for posterity, in >> > 99.999%of cases this is a very, very bad idea. It means you have to >> > go out of your way to test your code, which means the jars you're >> > producing most >> likely >> > won't be tested. >> > >> > Out of curiosity, what reason did you have for this? >> > >> > -john >> > >> > On 5/22/06, Max Cooper <[EMAIL PROTECTED]> wrote: >> > >> >> >> >> John, >> >> >> >> That worked! Thanks. I am pretty sure I read something about that >> >> before, so now I feel a bit silly to have asked. :-) >> >> >> >> Anyway, I was asking so that I could have maven.test.skip set to >> >> true >> by >> >> default, but still be able to override it on the command line. It >> seems >> >> like this should work without any trickery, but there is a bug in >> >> maven's handling of system properties that prevents it from >> >> working. With help from Kenney Westerhof and you, I've got a >> >> solution now. I am describing it here for anyone else that might >> >> need to do this, in >> hopes >> >> that they will find it in the mailing list archives. >> >> >> >> Put this in your settings.xml file to skip tests by default, while >> >> retaining the ability to run them by putting >> -Dmaven.test.skip=false on >> >> the command line: >> >> >> >> >> >> >> >> >> >> >> >>!maven.test.skip >> >> >> >> >> >> >> >> true >> >> >> >> >> >> >> >> -Max >> >> >> >> John Casey wrote: >> >> > Try: >> >> > >> >> > !X >> >> > >> >> > ...activated when the system property is undefined. >> >> > >> >> > >> >> >> X!Y> ivation> >> >> >> >> >> > >> >> > >> >> > ...activated when the system property's value is != Y. >> >> > >> >> > HTH, >> >> > >> >> > John >> >> > >> >> > On 5/22/06, Max Cooper <[EMAIL PROTECTED]> wrote: >> >> > >> >> >> >> >> >> I guess I should have been more clear. I want a profile to be >> active >> >> >> ONLY when the property X is NOT set. >> >> >> >> >> >> Here's my XML psuedo-code for what I want: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >>X >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> I have been playing with and using 'mvn >> >> >> help:active-profiles' to see what profiles are active, but I >> >> >> have >> not >> >> >> found a solution yet. >> >> >> >> >> >> -Max >> >> >> >> >> >> Allan Ramirez wrote: >> >> >> > Yes, set the profile in the settings.xml via >> >> >> > >> >> section. >> >> >> > >> >> >> >> >> >> http://maven.apache.org/guides/introduction/introduction-to-profiles. >> html >> >> >> > >> >> >> > Max Cooper wrote: >> >> >> > >> >> >> >> I know that I can make a profile active when a property is >> set... >> >> >> >> X >> >> >> >> >> >> >> >> Or when a property is set to a certain value... >> >> >> >> >> >> >> >> >> >> XY> vation> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Is there a way to make a profile active when a certain >> >> >> >> property >> is >> >> NOT >> >> >> >> set? >> >> >> >> >> >> >> >> Thanks, >> >> >> >> -Max >> >> >> >> >> >> >> >> >> >> -- >> >> --- >> >> >> >> To unsubs
RE: [m2] generating uml documentation
+1 name the reverse-engineering UML diagram plugin as "cough up fur ball". -Original Message- From: Dan Adams [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 7:11 AM To: 'Maven Users List' Subject: [m2] generating uml documentation Anyone know of a plugin to generate a uml diagram from the java classes and include it in the documentation? This would be immensely useful to me. -- Dan Adams Software Engineer Interactive Factory 617.235.5857 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [SOLVED] Re: mvn compile fails on Windows w/ JDK 1.5.0_06
It is not uncommon that YMMV with deployments of Java clients to Win XP
workstations.
For example there was gap in Win XP JRE packaging by Msoft for a period of time.
It places a burden on IT staff to ensure the correct service packs are
installed..
See prior thread..
http://www.nabble.com/forum/ViewPost.jtp?post=1762829&framed=y
Sean
-Original Message-
From: Kathryn Huxtable [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 21, 2006 11:24 AM
To: Maven Users List
Subject: Re: [SOLVED] Re: mvn compile fails on Windows w/ JDK 1.5.0_06
I think there are two different windows installers for the JDK. A zip file and
a windows installer. They may behave differently.
I use Mac OS X, my henchmen use Windows. I think I remember one of them having
a similar problem, but not with Maven.
On 3/21/06 1:13 PM, "Alexandre Poitras" <[EMAIL PROTECTED]> wrote:
--
Kathryn Huxtable
Middleware Architect
Core Middleware
Information Technology, a division of Information Services
The University of Kansas
> Windows mysteries :)
>
> On 3/21/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> wrote:
>> The re-install appears to have fixed the issue. Looking at the
>> contents of C:\Program Files\Java\jdk1.5.0_06, there appear to be
>> more files in there then under the previous install. The first
>> install must have been incomplete.
>>
>> I guess, if all else fails, re-install...
>>
>>
>> Ian
>>
>> It's better to be hated for who you are
>> than loved for who you are not
>>
>> Ian D. Stewart
>> Appl Dev Analyst-Advisory, DCS Automation
>> JPMorganChase Global Technology Infrastructure
>> Phone: (614) 244-2564
>> Pager: (888) 260-0078
>>
>>
>>
>> [EMAIL PROTECTED]
>> chase.comTo: "Maven Users List"
>>
>>cc:
>> 03/21/2006 09:43 Subject: Re: mvn compile
>> fails on Windows w/ JDK 1.5.0_06
>> AM
>> Please respond to
>> "Maven Users
>> List"
>>
>>
>>
>>
>>
>> Sounds like it may be something specific to my installation then.
>> Not quite the answer I was hoping for, but at least it's a start.
>>
>> I'll try uninstalling and reinstalling JDK 1.5.0_06 and see if that
>> gets me anywhere.
>>
>>
>> Ian
>>
>> It's better to be hated for who you are
>> than loved for who you are not
>>
>> Ian D. Stewart
>> Appl Dev Analyst-Advisory, DCS Automation
>> JPMorganChase Global Technology Infrastructure
>> Phone: (614) 244-2564
>> Pager: (888) 260-0078
>>
>>
>>
>> "Alexandre
>>
>> Poitras" To: "Maven Users
>> List"
>> >
>> @gmail.com> Subject: Re: mvn compile
>> fails on Windows w/ JDK 1.5.0_06
>>
>> 03/21/2006 08:56
>>
>> AM
>>
>> Please respond to
>>
>> "Maven Users List"
>>
>>
>>
>>
>>
>>
>> I have never seen this problem and I have both a jdk and a jre
>> installed.
>>
>> On 3/20/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>> wrote:
>>> Dear List,
>>>
>>> I recently upgraded my JDK from 1.5.0_04 to 1.5.0_06. Now when I
>>> run
>>>
>>> mvn compile
>>>
>>> I get the following error:
>>>
>>> Unable to locate the Javac Compiler in:
>>> C:\Program Files\Java\jre1.5.0_06\..\lib\tools.jar
>>> Please ensure you are using JDK 1.4 or above and
>>> not a JRE (the com.sun.tools.javac.Main class is required). In most
>>> cases you can change the location of your Java installation by
>>> setting the JAVA_HOME environment variable.
>>>
>>> Note that JAVA_HOME is set to C:\Program Files\Java\jdk1.5.0_06.
>>>
>>> There appears to be a built-in assumption somewhere within
>>> maven-compiler-plugin that ${java.home} == ${jre.home}\.. While
>>> this was true under jdk1.5.0_04, it is not the case with jdk1.5.0_06
>>> (The JDK is installed under C:\Program Files\Java\jdk1.5.0_06, while
>>> the JRE is installed under C:\Program Files\Java\jre1.5.0_06). I've
>>> tried tracking down the place in the code where this assumption is
>>> made, so that I could submit a patch, and got as far as
>>> org.codehaus.plexus.compiler.manager.CompilerManager, but I haven't
>>> been able to track down the location of the Plexus SVN repository to
>>> research further.
>>>
>>> Before I post a bug report, has any body else encountered this
>>> problem,
>> and
>>> is there a patch and/or work around available?
>>>
>>>
>>> Thanks,
>>> Ian
>>>
>>> It's better to be hated for who you are
>>> than loved for who you are not
>>>
>>> Ian D. Stewart
>>> Appl Dev Analyst-Advisory, DCS Automation
>>> JPMorganChase Global Technology Infrastructure
>>> Phone: (614) 244-2564
>>> Pager: (888) 260-0078
>>>
>>>
>>> ---
RE: M2 : Issue with echoproperties task with maven-antrun-plugin using Maven 2.0
See previous thread.. Subjext: [m2] antrun build.xml
RE: Repository 'central' will be blacklisted -- any clue?
Likely the [WARINING] [INFO] message is generic and we are seeing different flavors of repository access failures. The use of 'blacklisted' implies any further attempts will also fail. Have we done something to warrant such persona non grata treatment? It remains a mystery. -Original Message- From: Karthik V [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 9:18 AM To: Maven Users List Subject: Re: Repository 'central' will be blacklisted -- any clue? I can browse thru repo1 wth my browser .. my browser is set to "direct connection to Internet" and not 'auto-detect proxy' ... I havnt specified anything in settings.xml ... I deleted the whole repo, reinstalled maven etc. but no avail ... On 1/5/06, Tim Davies <[EMAIL PROTECTED]> wrote: > > It normally happens when maven fails to download an artifact. > > If you can browse ibiblio through a browser and your proxy settings > are the same in maven then theres no reason why it shouldnt work. > > I would suggest you delete the folder > "org\apache\maven\plugins\maven-install-plugin" from you local > repository and try again. It has maybe become corrupted in some way. > > > Mike Perham wrote: > > >Maybe the remote machine is down. Try a mirror or in a few hours. > > > >-Original Message- > >From: Karthik V [mailto:[EMAIL PROTECTED] > >Sent: Thursday, January 05, 2006 11:03 AM > >To: Maven Users List > >Subject: Re: Repository 'central' will be blacklisted -- any clue? > > > >yes i saw ur post at > >http://www.nabble.com/-m2-FC4-INFO-:-%22Repository-'central'-will-be- > >bla > >cklisted%22-p1875130.html... > >I'm running this on Win XP, and it was running fine till yesterday. > >Nothing changed on my side. If maven just does http downloads of the > >artifacts, why does it fail when I can still browse the Internet? Can > >this happen if something is changed in the gateway or the proxy? > > > > > > > >On 1/5/06, Sean Hennessy <[EMAIL PROTECTED]> wrote: > > > > > >>I ran into this behavior on another system when it was upgraded to > >>Fedora Core 4 and SELinux security was enabled by default. > >> > >>-Original Message- > >>From: Karthik V [mailto:[EMAIL PROTECTED] > >>Sent: Thursday, January 05, 2006 8:49 AM > >>To: Maven Users List > >>Subject: Repository 'central' will be blacklisted -- any clue? > >> > >> > >>Any clue about this error? > >> > >>[WARNING] repository metadata for: 'artifact > >>org.apache.maven.plugins:maven-inst > >>all-plugin' could not be retrieved from repository: central due to > >>an > >>error: Err or 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] > >> > >>-- > >>-- > >>- > >> > >> > >>All of a sudden everything stopped working, throwing this error. > >> > >> > >>- > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > >> > > > > > >- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Tim Davies > Analyst Developer > > KTS PLC: Service you can bank on > 8th Floor, Finsbury Tower, > 103-105 Bunhill Row, > London EC1Y 8LZ > tel: +44 (0)20 7256 2300 > fax: +44 (0)20 7256 2301 > > email: [EMAIL PROTECTED] > web: http://www.ktsplc.com > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Repository 'central' will be blacklisted -- any clue?
I ran into this behavior on another system when it was upgraded to Fedora Core 4 and SELinux security was enabled by default. -Original Message- From: Karthik V [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 8:49 AM To: Maven Users List Subject: Repository 'central' will be blacklisted -- any clue? Any clue about this error? [WARNING] repository metadata for: 'artifact org.apache.maven.plugins:maven-inst all-plugin' could not be retrieved from repository: central due to an error: Err or 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] - All of a sudden everything stopped working, throwing this error. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: antrun's antlr task problem
Not sure about maven.plugin.classpath however my use of maven.dependency.classpath seems to work as configured here. Perhaps using the name attribute used in the property element within the pom instead of maven.plugin.classpath? -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 10:35 PM To: Maven Users List Subject: Re: antrun's antlr task problem any one? ;-) On 1/4/06, dan tran <[EMAIL PROTECTED]> wrote: > > ok, have my plugin's configuration as > > > > > > > > > > and have my build.xml to reference maven.plugin.classpath, but got > error > > Embedded error: The following error occurred while executing this > line: > M:\dtran-uscud-dtran-phoenix-i\EJB\maven\openjms\build.xml:249: The > following er > ror occurred while executing this line: > M:\dtran-uscud-dtran-phoenix-i\EJB\maven\openjms\build.xml:279: Reference > maven. > plugin.classpath not found. > > > Suggestion on how to trouble shoot this issue is greatly appreciated. > > -Dan > > > > > > > On 1/4/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > > > > You need to use the plugin classpath in your build.xml and call > > with inheritRefs="true" > > > > > > > > On 1/4/06, dan tran <[EMAIL PROTECTED]> wrote: > > > Folks, > > > > > > Here is my build : > > > > > > > > > > > > maven-antrun-plugin > > > 1.1-SNAPSHOT > > > > > > > > > ant > > > ant-nodeps > > > 1.6.5 > > > > > > > > > antlr > > > antlr > > > 2.7.4 > > > > > > > > > > > > > > > > > > compile > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > run > > > > > > > > > > > > > > > > > > > > > > > > and antrun complains > > > > > > Embedded error: The following error occurred while executing this > > line: > > > M:\dtran-uscud-dtran-phoenix-i\EJB\maven\openjms\build.xml:299: > > > Could > > not > > > create > > > task or type of type: antlr. > > > > > > Ant could not find the task or a class this task relies upon. > > > > > > > > > > > > > > > > > > Any suggestions? > > > > > > Thanks > > > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JNI with maven2
FYI: http://mojo.codehaus.org instead of http://mojo.codehaus.com -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 9:22 AM To: Maven Users List Subject: Re: JNI with maven2 Philippe native-maven-plugin is at http://mojo.codehaus.com. Still in alpha, but I am able to compile windows and linux,etc. Give it a try, feedback + help is greatly appreciated. The doc is still very limitted. -D On 1/4/06, Philippe Faes <[EMAIL PROTECTED]> wrote: > > Hi all, > > I found a maven-1 plugin for compiling native code (for JNI), but none > for maven-2. Can I use m2 for my JNI project or is it not ready yet? > > kind regards > Philippe > > > -- > ir. Philippe Faes > Ghent University - Department ELIS > Sint-Pietersnieuwstraat 41 -- B-9000 Gent > Tel:+32 9 264 95 25 - Fax:+32 9 264 35 94 >http://www.elis.UGent.be/~pfaes > ON5DEU -- LPIC1 -- gpg-key:173720B6 > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] antrun build.xml
I am experimenting with document site generation and antrun support in
Maven version: 2.0.1.
I have antrun using a reduction of an ant tst.mvn.build.xml file results
in the following
"Could not create task or type of type: script." as found in the
included excerpts below.
Was the functionality excluded from ant-1.6.5.jar or is there
an additional dependency required in the pom on behalf of ant (like
beanshell)?
Thanks,
Sean
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] pom.xml: maven-antrun-plugin
[echo] pom.xml: timestamp 3-Jan-2006
[echo] basedir is E:\usr\local\share\sdf\exp\m2.0.1\shennessy
[echo] dotdir is E:\usr\local\share\sdf\exp\m2.0.1
[echo] dotdotdir is E:\usr\local\share\sdf\exp
[echo] prjrootdir is
E:\usr\local\share\sdf\exp\m2.0.1\shennessy/src
[echo] tst.mvn.build.xml: timestamp 3-Jan-2006
proj.doc:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: The following error occurred while executing this line:
E:\usr\local\share\sdf\exp\m2.0.1\shennessy\src\4.bin\tst.mvn.build.xml:
17: Could not create task or type of type: script.