Re: Maven 3.0.3 hanging / having timeouts often?
Okay, I removed a bunch of cruft from my settings.xml and odd settings that our company has asked us to put in there. Once cleaning this up I have not had the timeout yet. I think I am okay for a while, but will respond again if the problem comes back and I can provide more useful information. Thanks On Mon, May 16, 2011 at 5:52 PM, Benson Margulies wrote: > "Running a local nexus means never having to say --offline" > > On Mon, May 16, 2011 at 7:43 PM, Barrie Treloar > wrote: > > On Tue, May 17, 2011 at 3:04 AM, Benson Margulies > wrote: > >> Or if you quietly put a copy of Archiva or Nexus for those purposes on > >> your own machine :-) > > > > Running a repository manager locally is a smart idea if you are on a > laptop. > > Saves you the pain of reconfiguring maven when you unplug from the > network. > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Maven 3.0.3 hanging / having timeouts often?
Archiva is being used to serve our internal packages of our company, it is not being used to serve dependencies from internet repositories. So no I cannot send all requests through Archiva. It may be as simple as a linux kernel issue with e1000e driver (dell latitude E6410). It has caused me issues in Ubuntu in 10.10 and could be still some issues in 11.04. It is hard to say as there is not much to debug with at this point and I am not seeing any obvious system errors or anything to troubleshoot with. On Mon, May 16, 2011 at 10:34 AM, Wayne Fay wrote: > > Any advice on this? Should I be opening a maven bug? It is really killing > my > > productivity as I have to babysit every build and keep aborting it and > > restarting it several times until all updates (mostly snapshots per day) > are > > downloaded. > > If this was typical then we would see similar complaints from lots of > people. Clearly something is special about the way you have things > configured or something else in your environment. I'm not sure how you > expect anyone here to diagnose this class of problem. > > Did you reconfigure your proxy and settings.xml so all requests are > going through Archiva? I see that as a pre-requisite before talking > about anything else. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Maven 3.0.3 hanging / having timeouts often?
Any advice on this? Should I be opening a maven bug? It is really killing my productivity as I have to babysit every build and keep aborting it and restarting it several times until all updates (mostly snapshots per day) are downloaded. Thanks, Andrew On Thu, May 12, 2011 at 5:39 AM, Alex Lopez wrote: > > > Em 12-05-2011 12:02, Tim Pizey escreveu: > > On 12 May 2011 11:50, Alex Lopez wrote: >> >>> >>> Em 12-05-2011 01:22, Andrew Robinson escreveu: >>> >>>> >>>> I have been using maven 2.2.1 for a while at my company and we just >>>> switched >>>> to maven 3. I have rebuilt my computer (ubuntu maverick 10.04 32-bit ==> >>>> ubuntu natty 11.04 64-bit) and installed maven 3. >>>> >>>> In maven 3.0.3, (I have not seen it with maven 2.2.1), it stops >>>> downloading >>>> after a few to several downloads. If I ^C the build, and keep re-running >>>> it, >>>> >>> >>> +1, I've been having this kind of 'hangs', using maven 3.0.2 and >>> artifactory >>> 2.3.1 (sometimes when running maven site, sometimes performing a build), >>> then ^C seems to get maven to continue doing what it was doing and >>> eventually end with success... >>> >> >> Me too, on win7/cygwin. I thought it was a cygwin problem. >> > > +1 now that I think about that it seems definitely like a cygwin problem, > since I'm never getting this through m2eclipse... > > could it be related with the warning cygwin gives me complaining about bad > ms-dos style paths? > > $ mvn site site:stage > cygwin warning: > MS-DOS style path detected: C:\Program Files\Apache Software > Foundation\apache-maven-3.0.2/boot/ > Preferred POSIX equivalent is: /cygdrive/c/Program Files/Apache Software > Foundation/apache-maven-3.0.2/boot/ > ... > > > >> cheers >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Maven 3.0.3 hanging / having timeouts often?
Okay, good to know, I'll forward that question onto the fellas that configured our settings.xml and pom.xml files for mvn3. On Thu, May 12, 2011 at 10:12 AM, Wayne Fay wrote: > > They are going through my proxy, why would you think I am hitting them > > directly? > > I'm OK with the proxy. I'm confused about the Archiva repo you have > installed. I should not have said "proxy" when I really meant > MRM/Archiva. Your log shows that your build is hitting Archiva and > then also hitting repo2, repo1, and ibiblio for a metadata.xml file. > > For us (and I think a lot of users of MRMs like Nexus, Artifactory, > Archiva), a large part of the reason why we are using a Maven Repo > Manager is so that we can tell all our Maven instances on all our > machines to look for ALL artifacts directly in that repo manager > (Archiva in your case). Then our governance functions can determine > which artifacts are OK to use (based on licensing and other concerns) > and which must be avoided etc. > > I think the way you have things configured is less than ideal and you > may want to reconsider it. IMO all artifact access should be managed > by your Archiva instance. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Maven 3.0.3 hanging / having timeouts often?
They are going through my proxy, why would you think I am hitting them directly? I have my setup in my settings.xml. It is working most of the time, if it were the fact that my proxy was not used, it would fail 100% of the time (all internet traffic must go through our proxy at work). -Andrew On Wed, May 11, 2011 at 9:01 PM, Wayne Fay wrote: > > Downloading: > > > http://internalserver.ouritranet.com:8086/archiva/repository/internal/org/apache/maven/skins/maven-default-skin/maven-metadata.xml > > > http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml > > > http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml > > > http://www.ibiblio.org/maven/org/apache/maven/skins/maven-default-skin/maven-metadata.xml > > Obviously you have a proxy. Why in the world are you connecting > directly to repo2, repo1, ibiblio etc instead of just letting your > proxy hit them on your behalf? > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Maven 3.0.3 hanging / having timeouts often?
I have been using maven 2.2.1 for a while at my company and we just switched to maven 3. I have rebuilt my computer (ubuntu maverick 10.04 32-bit ==> ubuntu natty 11.04 64-bit) and installed maven 3. In maven 3.0.3, (I have not seen it with maven 2.2.1), it stops downloading after a few to several downloads. If I ^C the build, and keep re-running it, it will eventually built. It only dies when maven is trying to download file. It may happen before any progress is display, partial progress or full progress. Example: Downloading: http://internalserver.ouritranet.com:8086/archiva/repository/internal/org/apache/maven/skins/maven-default-skin/maven-metadata.xml Downloading: http:// internalserver.ouritranet.com:8086/archiva/repository/snapshots-corporate/org/apache/maven/skins/maven-default-skin/maven-metadata.xml Downloading: http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml Downloading: http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml Downloading: http://www.ibiblio.org/maven/org/apache/maven/skins/maven-default-skin/maven-metadata.xml 341 B 341 B If I let it go for a while it then prints: Downloading: http://internalserver.ouritranet.com:8086/archiva/repository/internal/org/apache/maven/skins/maven-default-skin/maven-metadata.xml Downloading: http://internalserver.ouritranet.com:8086/archiva/repository/snapshots-corporate/org/apache/maven/skins/maven-default-skin/maven-metadata.xml Downloading: http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml Downloading: http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml Downloading: http://www.ibiblio.org/maven/org/apache/maven/skins/maven-default-skin/maven-metadata.xml [WARNING] Checksum validation failed, could not read expected checksum: Error transferring file: Connection timed out for http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml [WARNING] Checksum validation failed, could not read expected checksum: Error transferring file: Connection timed out for http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml My other co-workers have not reported seeing this issue yet. Any ideas on why maven 3.0.3 is having this problem when maven 2.2.1 does not? FYI, we have a corporate proxy, not sure if that could be part of the problem. -Andrew
Using maven-exec-plugin as a non-reusable plugin?
It is sometimes very convenient to have a java class with a main method used to help build a maven project, but one that is so specific to that project that it is too large of an overhead to author it as a reusable maven plugin. Using maven-exec-plugin, the class can be run, but then the question becomes who will compile it? Since the class is only used by the build, it should not be included in the produced artifact (jar, war, etc), but the maven-compiler-plugin is not written to taken configured source and destination directories, only to use project-wide directories. Is there a better solution than to just filter the classes out of the built artifact, or another way to build code to be used like a plugin, but without the full need to support the plugin as a reusable tool?
Re: maven-site-plugin no longer multi-module?
Thanks, I'll take the ".", "maven." and ".version" into consideration for our pom, but that is unrelated to the issue at hand. Either way it is done, the site 2.1.1 plug-in does not execute the site for the modules, only for the parent projects site directory. When I get a chance, I will put together a test case and submit a bug. It seems that there are several problems with the maven site, doxia and related plugins in maven 2.2.1. I hope to site the site plugin more mature in the next maven release. On Wed, Oct 6, 2010 at 8:45 PM, Wayne Fay wrote: >> My guess is that while dots are in general perhaps ill-advised, >> 'maven.' is what really causes the problem here. In my experience, >> dots in pom props are as common as dirt, and it's very much news to me >> that they are a bad idea. There are a lot of poms at Apache that will >> need to be edited if all dots are equally bad in prop names. > > At some point, there was a Maven bug that basically evaluated > ${*.version} as equivalent to ${version} and so people were getting > their current project version in all kinds of places they didn't > expect. Ever since then, I've avoided dots in my properties names and > told people to avoid them likewise. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-site-plugin no longer multi-module?
I am trying to get our build system moved over from maven 2.0.8 to 2.2.1, but we have been having problems with the site plugin. While converting over, I am supporting a profile that changes the plugin version. Here is the setup: ... 2.0.1 ... ... org.apache.maven.plugins maven-site-plugin ${maven.site.plugin.version} commons-httpclient commons-httpclient 3.1 commons-logging commons-logging ... ... siteFix false 2.1.1 ... When I execute "mvn site" from the top level pom directory in maven 2.0.8, it builds the site for the top directory and all of the modules. If I execute "mvn -PsiteFix site" from maven 2.2.1, it does not build the modules and only builds the site for the current directory. Is there a way to get this to function as it did before? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Activation based on maven version?
I would like to perform an activation based on maven version (for my needs I would like to know maven > 2.0.8). Is there any way to do this? I noticed this has been filed and not resolved: http://jira.codehaus.org/browse/MNG-4760 Basically I want to change a plugin to use a certain version for maven 2.2.1 but not 2.0.8. Thanks, Andrew - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: http://jira.codehaus.org/browse/MPIR-194 is killing the build
Of course, right after I send the email I got it to work: org.apache.maven.plugins maven-site-plugin 2.1.1 commons-httpclient commons-httpclient 3.1 commons-logging commons-logging The warnings still print, but the build succeeded. On Tue, Aug 24, 2010 at 4:14 PM, Andrew Robinson wrote: > I am having problems getting our maven site build to work in any but 2.0.8. > > In builds after 2.0.8 (including maven 2.2.1), we are getting the > exception "java.lang.ArrayIndexOutOfBoundsException: 1" (see below). > This appears to be the error in > http://jira.codehaus.org/browse/MPIR-194 > > [INFO] Generating "Continuous Integration" report. > [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink > instance and no SinkFactory available. Please update this plugin. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] 1 > [INFO] > > [DEBUG] Trace > java.lang.ArrayIndexOutOfBoundsException: 1 > at > org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791) > > If I try to run a newer maven-site-plugin I hit other bugs. > For maven-site-plugin 2.1.1 and 2.1 I get the error for > http://jira.codehaus.org/browse/DOXIA-394: > > org.apache.commons.logging.LogConfigurationException: > org.apache.commons.logging.LogConfigurationException: > org.apache.commons.logging.LogConfigurationException: Invalid class > loader hierarchy. You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed. > (Caused by org.apache.commons.logging.LogConfigurationException: > Invalid class loader hierarchy. You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed.) > (Caused by org.apache.commons.logging.LogConfigurationException: > org.apache.commons.logging.LogConfigurationException: Invalid class > loader hierarchy. You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed. > (Caused by org.apache.commons.logging.LogConfigurationException: > Invalid class loader hierarchy. You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed.)) > at > org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543) > > > I have tried forcing maven 2.2.1 to use doxia 1.0 from maven 2.0.8, > but there seem to be too many plugins and master pom files and other > libraries that are forcing a newer doxia version. > > I have a product that is being used by users and cannot use a maven > beta release (3.0) to try the 3.0-beta-1 site plugin version. > > At one point I even hit http://jira.codehaus.org/browse/MSITE-440 and > not in offline mode. > > I find it hard to believe with so many maven releases beyond 2.0.8 > that there is no way to get the site plugin working. What magic > incantations do I need to perform to get a working site build in maven > 2.2.1? I would really appreciate any help. > > > This did not work trying to force doxia 1.0: > > org.apache.maven.plugins > maven-site-plugin > 2.0.1 > > > org.apache.maven.plugins > maven-javadoc-plugin > 2.4 > > > org.apache.maven.plugins > maven-project-info-reports-plugin > 2.1.2 > > > org.apache.maven.plugins > maven-pmd-plugin > 2.4 > > > It looks like maybe internal jars to maven is forcing a newer doxia version? > > Thank you, > Andrew > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
http://jira.codehaus.org/browse/MPIR-194 is killing the build
I am having problems getting our maven site build to work in any but 2.0.8. In builds after 2.0.8 (including maven 2.2.1), we are getting the exception "java.lang.ArrayIndexOutOfBoundsException: 1" (see below). This appears to be the error in http://jira.codehaus.org/browse/MPIR-194 [INFO] Generating "Continuous Integration" report. [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. Please update this plugin. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] 1 [INFO] [DEBUG] Trace java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791) If I try to run a newer maven-site-plugin I hit other bugs. For maven-site-plugin 2.1.1 and 2.1 I get the error for http://jira.codehaus.org/browse/DOXIA-394: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.) (Caused by org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.)) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543) I have tried forcing maven 2.2.1 to use doxia 1.0 from maven 2.0.8, but there seem to be too many plugins and master pom files and other libraries that are forcing a newer doxia version. I have a product that is being used by users and cannot use a maven beta release (3.0) to try the 3.0-beta-1 site plugin version. At one point I even hit http://jira.codehaus.org/browse/MSITE-440 and not in offline mode. I find it hard to believe with so many maven releases beyond 2.0.8 that there is no way to get the site plugin working. What magic incantations do I need to perform to get a working site build in maven 2.2.1? I would really appreciate any help. This did not work trying to force doxia 1.0: org.apache.maven.plugins maven-site-plugin 2.0.1 org.apache.maven.plugins maven-javadoc-plugin 2.4 org.apache.maven.plugins maven-project-info-reports-plugin 2.1.2 org.apache.maven.plugins maven-pmd-plugin 2.4 It looks like maybe internal jars to maven is forcing a newer doxia version? Thank you, Andrew - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Generating an XPI file from maven2?
I have looked over Google, and I have not seen a satisfactory answer to this extremely simple requirement. I am trying to produce an XPI file for a firefox extension. An XPI file is simply a zip file with a different extension. I have looked at the maven-jar-plugin and the maven-assembly-plugin and both are too restrictive to be able to use correctly it seems. If I use a jar project, I have the following problems: 1) it insists on adding the ".jar" extension to the file 2) there seems to be no way to stop the manifest from being added I have looked at the maven-assembly-plugin. I have the following problems: 1) It doesn't seem to easily include the section of the pom for a pom type project 2) it insists on adding the ".zip" extension to the file All I want is what a jar project does but I want my own extension (xpi, not jar) and I do not want the META-INF directory to be created. I would create my own plug-in, but there doesn't seem to be a way to create a mojo file in the same project (I don't want to have to build a re-usable plugin, import its references into the project, deploy it, etc. just for this one project). Is this the only option? And if so, is there a way to make the plugin so that it only is used by this one project and is never deployed to a repository (sub-directory for example)? Also, the XPI plug-in on source-force is no use to me as it is for the legacy XPI layout. Thanks, Andrew - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Wierd issue with getting a resource from inside a jar
How is this a weird issue? URL != file. Just because some URLs can be converted to valid files doesn't mean all can. If you need the file contents use getResourceStream. If you need information on the file, use the java.util.zip package Sent from my iPod On Oct 26, 2008, at 4:34 AM, "Jeffrey Williams" <[EMAIL PROTECTED] > wrote: Hi, I am having an issue with maven and getting a file from within my executable jar project. I have the following code in my main URL url = this.getClass().getResource("/comma.txt"); File commaFile = new File(url.getFile()); The issue is that the url that is found when executing the jar has an exclamation mark in it. ie /home/jeffxor/workspace/cyrus/target/cyrus-0.0.1-SNAPSHOT.jar!/ comma.txt you will notice it after the jar file name. Obviously when I then try to get a file I get FileNotFoundException. I have used this code on other machine and have had no issue. I am using Ubuntu and maven 2.0.8 and java 1.6., I have searched the internet but have got no results and I am out of ideas. Any help would be great. - 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: Launching more than one program
configure 2 executions of the maven-exec-plugin, one for each of you classes. Instead of using plugin/configuration use plugin/executions/execution/configuration to setup the settings. -Andrew On Thu, Oct 2, 2008 at 12:21 PM, Trevor Harmon <[EMAIL PROTECTED]> wrote: > In Ant, I am used to launching programs like this: > > > > > > > > > > > > > > ant foo --> launches Foo with parameter -abc > ant bar --> launches Bar with parameter -xyz > > This doesn't seem to be possible in Maven. The problem, apparently, is that > the exec:java goal maps to one and only one program. In other words, all I > can do is this: > > mvn exec:java > > I can set it up to launch Foo or Bar, but it can't handle both. > > Is there a way around this? > > Trevor > > > - > 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: command line debug args for jetty plugin?
jetty runs inside of maven, so just pass those settings in your MAVEN_OPTS environment variable and attach to maven. That has worked for me. -Andrew On Thu, Oct 2, 2008 at 1:48 PM, Mick Knutson <[EMAIL PROTECTED]> wrote: > I am trying to connect to my Jetty application, but want to know how to add > the following to the jetty plugin: > > -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 > > > > -- > --- > Thank You… > > Mick Knutson > BASE Logic, inc. > (415) 354-4215 > > Website: http://baselogic.com > Blog: http://baselogic.com/blog > BLiNC Magazine: http://blincmagazine.com > Linked IN: http://linkedin.com/in/mickknutson > DJ Mick: http://djmick.com > MySpace: http://myspace.com/mickknutson > Vacation Rental: http://tahoe.baselogic.com > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Build error with jython plugin !!??
Set the groupId of the plugin: com.servprise.maven.plugins Their instructions seem odd to me (creating a dependency instead of setting the version and group in the plugin tag). Give this a try instead of using a : maven-jython-plugin com.servprise.maven.plugins 0.3 compile C:\jython2.2.1 compile On Tue, Sep 30, 2008 at 6:25 AM, miata <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm new user of maven and I want use the jython plugin but I have a problem > at compilation... This is the error : > The plugin 'org.apache.maven.plugins:maven-jython-plugin' does not exist or > no valid version could be found > > It's use in a new project and his configuration pom is very simple : > > >maven-jython-plugin > > >compile > > C:\jython2.2.1 > > > compile > > > > > > > > > Servprise Repository > http://dev.servprise.com/maven-repository > > > > > > com.servprise.maven.plugins > maven-jython-plugin > 0.3 > compile > > > > My m2Repository have the plugin, the version is good and the plugin has been > add into the project... > I don't understand this problem compilation, if someone has an idea to > resolve ??? > > thanks > -- > View this message in context: > http://www.nabble.com/Build-error-with-jython-plugin-%21%21---tp19741002p19741002.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]
Jetty and using src/test/webapp
I have a war project that was built that also has a "src/test/webapp" directory. The idea was that test pages could be made in this directory that would not be included in the normal war. I have got it mostly working except for the classes. I need to have both target/classes and target/test-classes on the classpath. Here is what I have been attempting to use: org.mortbay.jetty maven-jetty-plugin 6.1.12.rc2 10 ${basedir}/src/test/webapp/WEB-INF/web.xml ${basedir}/src/test/webapp /demo-test src/test/webapp,src/main/webapp Looking here: http://docs.codehaus.org/display/JETTY/Which+files+are+scanned+by+the+Jetty+Maven+Plugin It says that scanTargets are picked up, but that did not work. I set classesDirectory to "${basedir}/target/test-classes", but then the "${basedir}/target/classes" were no longer on the classpath. How can I get jetty to run off of the src/test/webapp and include both "${basedir}/target/test-classes" and "${basedir}/target/classes"? Thanks, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem of resolving eclipse swt linux library
Forgot my win32.xml that is in my src/main/assembly/jar folder: http://maven.apache.org/POM/4.0.0"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> win32 jar false true true provided org.eclipse:swt-win32 On Wed, Aug 27, 2008 at 11:42 AM, Andrew Robinson <[EMAIL PROTECTED]> wrote: > My pom is huge, but here are some snippets: > ... > > ... >3.3.2 > > > ... > > ... > > > org.eclipse > eclipse-jface > ${eclipse-version} > > > > org.eclipse > eclipse-equinox-common > ${eclipse-version} > > > > org.eclipse > eclipse-core-commands > ${eclipse-version} > > > > org.eclipse > eclipse-osgi > ${eclipse-version} > > > > org.eclipse > eclipse-ui-workbench > ${eclipse-version} > > > > > org.eclipse > swt-gtk-linux-x86 > ${eclipse-version} > provided > > > > org.eclipse > swt-gtk-linux-x86_64 > ${eclipse-version} > provided > > > > org.eclipse > swt-win32 > ${eclipse-version} > provided > > > > org.eclipse > macosx-swt > ${eclipse-version} > provided > > ... > > ... > >maven-assembly-plugin >2.2-beta-2 > > >make-jar >package > > attached > > > false > > src/main/assembly/jar/ > > > mypackage.MyMainClass > > > > > >make-assembly >package > > attached > > > > src/main/assembly/package/ > > > > > ... > > > Here is an example of my win32.xml file in the > src/main/assembly/package directory: > > > > xmlns="http://maven.apache.org/POM/4.0.0"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > win32 > >zip > > > > true > / > src/main/assembly/windows/runMyApplication.cmd > > > ${pom.artifactId}-${pom.version}.jar > target/${pom.artifactId}-${pom.version}-win32.jar > > > > > Hope that helps, > Andrew > > On Wed, Aug 27, 2008 at 9:09 AM, Carfield Yim <[EMAIL PROTECTED]> wrote: >> >> So you are creating a jar with correct dependence classes and run test base >> on that jar? Not sure how can I do that... would you sure you pom.xml for me >> to refer to? >> >> >> Andrew Robinson-5 wrote: >>> >>> I used the maven assembly plugin to pull in the correct Jar. I have >>> all 3 jars (linux, Mac and Windows) as "provided" so that they are >>> there for compilation but they don't get automatically included in the >>> release. You can also have a profile to trigger on the correct current >>> OS, but that will not help you for releases, as you may want to >>> package a windows build on Linux. >>> >>> -Andrew >>> >>> On Tue, Aug 26, 2008 at 1:23 PM, Carfield Yim <[EMAIL PROTECTED]> >>> wrote: >>>> >>>> Actually what I like to do is to tell maven to use >>>> System.getProperty("user.os") and select the right dependence, is that >>>> possible? >>>> >>>> >>>> Carfield Yim wrote: >>>>> >>>>> I see... thanks, now I can resolve and download the correct swt library. >>>>> However, we would like to make the test running with maven correctly for >>>>> Windows and Linux. How can I tell maven to use correct platform of >>>>> library? >>>>> >>>>> >>>>> lukewpatterson wrote: >>>>>> >>>>>> These are in the repo >>>>>> >>>>>> org.eclipse.swt.gtk.linux >>>>>> x86_64 >>>>>> [1] >&g
Re: Problem of resolving eclipse swt linux library
My pom is huge, but here are some snippets: ... ... 3.3.2 ... ... org.eclipse eclipse-jface ${eclipse-version} org.eclipse eclipse-equinox-common ${eclipse-version} org.eclipse eclipse-core-commands ${eclipse-version} org.eclipse eclipse-osgi ${eclipse-version} org.eclipse eclipse-ui-workbench ${eclipse-version} org.eclipse swt-gtk-linux-x86 ${eclipse-version} provided org.eclipse swt-gtk-linux-x86_64 ${eclipse-version} provided org.eclipse swt-win32 ${eclipse-version} provided org.eclipse macosx-swt ${eclipse-version} provided ... ... maven-assembly-plugin 2.2-beta-2 make-jar package attached false src/main/assembly/jar/ mypackage.MyMainClass make-assembly package attached src/main/assembly/package/ ... Here is an example of my win32.xml file in the src/main/assembly/package directory: http://maven.apache.org/POM/4.0.0"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> win32 zip true / src/main/assembly/windows/runMyApplication.cmd ${pom.artifactId}-${pom.version}.jar target/${pom.artifactId}-${pom.version}-win32.jar Hope that helps, Andrew On Wed, Aug 27, 2008 at 9:09 AM, Carfield Yim <[EMAIL PROTECTED]> wrote: > > So you are creating a jar with correct dependence classes and run test base > on that jar? Not sure how can I do that... would you sure you pom.xml for me > to refer to? > > > Andrew Robinson-5 wrote: >> >> I used the maven assembly plugin to pull in the correct Jar. I have >> all 3 jars (linux, Mac and Windows) as "provided" so that they are >> there for compilation but they don't get automatically included in the >> release. You can also have a profile to trigger on the correct current >> OS, but that will not help you for releases, as you may want to >> package a windows build on Linux. >> >> -Andrew >> >> On Tue, Aug 26, 2008 at 1:23 PM, Carfield Yim <[EMAIL PROTECTED]> >> wrote: >>> >>> Actually what I like to do is to tell maven to use >>> System.getProperty("user.os") and select the right dependence, is that >>> possible? >>> >>> >>> Carfield Yim wrote: >>>> >>>> I see... thanks, now I can resolve and download the correct swt library. >>>> However, we would like to make the test running with maven correctly for >>>> Windows and Linux. How can I tell maven to use correct platform of >>>> library? >>>> >>>> >>>> lukewpatterson wrote: >>>>> >>>>> These are in the repo >>>>> >>>>> org.eclipse.swt.gtk.linux >>>>> x86_64 >>>>> [1] >>>>> >>>>> org.eclipse.swt.gtk.linux >>>>> x86 >>>>> [2] >>>>> >>>>> The (groupId/artifactId)s are different than what you had listed. >>>>> >>>>> >>>>> >>>>> [1] - >>>>> http://repo1.maven.org/maven2/org/eclipse/swt/gtk/linux/x86_64/3.3.0-v3346/ >>>>> [2] - >>>>> http://repo1.maven.org/maven2/org/eclipse/swt/gtk/linux/x86/3.3.0-v3346/ >>>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Problem-of-resolving-eclipse-swt-linux-library-tp19103219p19168597.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] >> >> >> > -- > View this message in context: > http://www.nabble.com/Problem-of-resolving-eclipse-swt-linux-library-tp19103219p19183049.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: Problem of resolving eclipse swt linux library
I used the maven assembly plugin to pull in the correct Jar. I have all 3 jars (linux, Mac and Windows) as "provided" so that they are there for compilation but they don't get automatically included in the release. You can also have a profile to trigger on the correct current OS, but that will not help you for releases, as you may want to package a windows build on Linux. -Andrew On Tue, Aug 26, 2008 at 1:23 PM, Carfield Yim <[EMAIL PROTECTED]> wrote: > > Actually what I like to do is to tell maven to use > System.getProperty("user.os") and select the right dependence, is that > possible? > > > Carfield Yim wrote: >> >> I see... thanks, now I can resolve and download the correct swt library. >> However, we would like to make the test running with maven correctly for >> Windows and Linux. How can I tell maven to use correct platform of >> library? >> >> >> lukewpatterson wrote: >>> >>> These are in the repo >>> >>> org.eclipse.swt.gtk.linux >>> x86_64 >>> [1] >>> >>> org.eclipse.swt.gtk.linux >>> x86 >>> [2] >>> >>> The (groupId/artifactId)s are different than what you had listed. >>> >>> >>> >>> [1] - >>> http://repo1.maven.org/maven2/org/eclipse/swt/gtk/linux/x86_64/3.3.0-v3346/ >>> [2] - >>> http://repo1.maven.org/maven2/org/eclipse/swt/gtk/linux/x86/3.3.0-v3346/ >>> >> >> > > -- > View this message in context: > http://www.nabble.com/Problem-of-resolving-eclipse-swt-linux-library-tp19103219p19168597.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: Problem of resolving eclipse swt linux library
BTW, if you plan on using JFace, do not use the libraries from maven, use your own from eclipse. The maven pom files for the uploaded SWT and JFace jars are incompatible. I found it much easier to install my own jars into my local repo than trying to fight the versions that are in the central repositories. On Fri, Aug 22, 2008 at 2:12 AM, Carfield Yim <[EMAIL PROTECTED]> wrote: > > I try to add eclipse swt linux library to my project. Thus, I add following > library to the pom.xml > > > org.eclipse.swt > org.eclipse.swt.gtk.linux.x86_64 > 3.3.0-v3346 > provided > > > org.eclipse.swt > org.eclipse.swt.gtk.linux.x86 > 3.3.0-v3346 > provided > > > However, maven complaint cannot be find > > Missing: > -- > 1) org.eclipse.swt:org.eclipse.swt.gtk.linux.x86:jar:3.3.0-v3346 > > However, when I check maven repo, it is there - > http://repo1.maven.org/maven2/org/eclipse/swt/gtk/linux/x86_64/ Anyone know > what is the problem? I have tried to use version 3.30 as win32 does, but it > failed also, any idea? > -- > View this message in context: > http://www.nabble.com/Problem-of-resolving-eclipse-swt-linux-library-tp19103219p19103219.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: get active profile in pom
There is no such thing as an active profile that I know of. There are active profile*s*. If you want to know if one particular profile is enabled, set a property in that profile and then test or use that profile elsewhere. -Andrew On Mon, Jul 7, 2008 at 10:47 AM, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote: > I will assume that there is no way to get a hold on active profile in pom > file. > > > On Sat, Jul 5, 2008 at 3:34 PM, Arash Bizhan zadeh <[EMAIL PROTECTED]> > wrote: > >> Hi all, >> Is there any variable to return active profile in the maven 2; (something >> like ${maven.profile})? >> >> thanks >> -- >> The dirtiest book of all is the expurgated book. >> >> Walt Whitman > > > > > -- > The dirtiest book of all is the expurgated book. > > Walt Whitman > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Need to generate simple runner script
actually you may be able to use pom.version, it was the site plugin that doesn't like dots because it uses velocity. On 2008-06-28, Andrew Robinson <[EMAIL PROTECTED]> wrote: > I just did something like this. Just use the maven assembly plugin to > package your app as a zip, tar or whatever. It can filter ${ in the > files. It is documented as not liking . In the names though. Steps (I > am on my iPod so this is not 100% accurate): > > 1) add a poroperty to your pom.xml: > ${pom.version} > 2) add a files tag to your assembly descriptor: > truesrc/main/assembly/runapp.sh > 3) then just use ${curruentVersion} in that file > > Andrew > > On 2008-06-27, Kathryn Huxtable <[EMAIL PROTECTED]> wrote: >> Actually, it turns out that the appassembler plugin is almost what I >> want. It requires that the project be installed to be included in the >> classpath and I'd rather run my project jar from the target directory. >> >> My purpose here is to provide a way for people who modify the source >> to test their mods without installing and such. It would be more >> streamlined. >> >> My distribution profile, which uses the assembly plugin, packages the >> project jar into a lib directory along with the dependencies. Then I >> can use Dawid Weiss's invoker jar (not in Maven, unfortunately) to >> automagically put everything in that directory into the classpath. >> >> -K >> >> On Jun 27, 2008, at 10:34 AM, Kathryn Huxtable wrote: >> >>> I am using the jar plugin to add the dependencies to the manifest of >>> my project's jar, and the dependencies plugin to create a lib >>> directory to contain them. I like that my jar has the version number >>> appended. >>> >>> Given that, is there any way to inject the version number into a >>> shell script and a Windows batch file to create runner scripts >>> during packaging? The essence of the script would be a line of the >>> form: >>> >>> java -jar target/artifactId-version.jar $* >>> >>> or something like that. >>> >>> I've looked at Codehaus's appassembler plugin and it does too much. >>> I haven't really looked at Codehaus's xslt plugin, but maybe that's >>> the way to go. >>> >>> Any ideas? >>> >>> -K, who has always gotten good suggestions from this list. >>> >>> >>> - >>> 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: Need to generate simple runner script
On 2008-06-28, Andrew Robinson <[EMAIL PROTECTED]> wrote: > actually you may be able to use pom.version, it was the site plugin > that doesn't like dots because it uses velocity. > > On 2008-06-28, Andrew Robinson <[EMAIL PROTECTED]> wrote: >> I just did something like this. Just use the maven assembly plugin to >> package your app as a zip, tar or whatever. It can filter ${ in the >> files. It is documented as not liking . In the names though. Steps (I >> am on my iPod so this is not 100% accurate): >> >> 1) add a poroperty to your pom.xml: >> ${pom.version} >> 2) add a files tag to your assembly descriptor: >> truesrc/main/assembly/runapp.sh >> 3) then just use ${curruentVersion} in that file >> >> Andrew >> >> On 2008-06-27, Kathryn Huxtable <[EMAIL PROTECTED]> wrote: >>> Actually, it turns out that the appassembler plugin is almost what I >>> want. It requires that the project be installed to be included in the >>> classpath and I'd rather run my project jar from the target directory. >>> >>> My purpose here is to provide a way for people who modify the source >>> to test their mods without installing and such. It would be more >>> streamlined. >>> >>> My distribution profile, which uses the assembly plugin, packages the >>> project jar into a lib directory along with the dependencies. Then I >>> can use Dawid Weiss's invoker jar (not in Maven, unfortunately) to >>> automagically put everything in that directory into the classpath. >>> >>> -K >>> >>> On Jun 27, 2008, at 10:34 AM, Kathryn Huxtable wrote: >>> >>>> I am using the jar plugin to add the dependencies to the manifest of >>>> my project's jar, and the dependencies plugin to create a lib >>>> directory to contain them. I like that my jar has the version number >>>> appended. >>>> >>>> Given that, is there any way to inject the version number into a >>>> shell script and a Windows batch file to create runner scripts >>>> during packaging? The essence of the script would be a line of the >>>> form: >>>> >>>>java -jar target/artifactId-version.jar $* >>>> >>>> or something like that. >>>> >>>> I've looked at Codehaus's appassembler plugin and it does too much. >>>> I haven't really looked at Codehaus's xslt plugin, but maybe that's >>>> the way to go. >>>> >>>> Any ideas? >>>> >>>> -K, who has always gotten good suggestions from this list. >>>> >>>> >>>> - >>>> 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: Need to generate simple runner script
I just did something like this. Just use the maven assembly plugin to package your app as a zip, tar or whatever. It can filter ${ in the files. It is documented as not liking . In the names though. Steps (I am on my iPod so this is not 100% accurate): 1) add a poroperty to your pom.xml: ${pom.version} 2) add a files tag to your assembly descriptor: truesrc/main/assembly/runapp.sh 3) then just use ${curruentVersion} in that file Andrew On 2008-06-27, Kathryn Huxtable <[EMAIL PROTECTED]> wrote: > Actually, it turns out that the appassembler plugin is almost what I > want. It requires that the project be installed to be included in the > classpath and I'd rather run my project jar from the target directory. > > My purpose here is to provide a way for people who modify the source > to test their mods without installing and such. It would be more > streamlined. > > My distribution profile, which uses the assembly plugin, packages the > project jar into a lib directory along with the dependencies. Then I > can use Dawid Weiss's invoker jar (not in Maven, unfortunately) to > automagically put everything in that directory into the classpath. > > -K > > On Jun 27, 2008, at 10:34 AM, Kathryn Huxtable wrote: > >> I am using the jar plugin to add the dependencies to the manifest of >> my project's jar, and the dependencies plugin to create a lib >> directory to contain them. I like that my jar has the version number >> appended. >> >> Given that, is there any way to inject the version number into a >> shell script and a Windows batch file to create runner scripts >> during packaging? The essence of the script would be a line of the >> form: >> >> java -jar target/artifactId-version.jar $* >> >> or something like that. >> >> I've looked at Codehaus's appassembler plugin and it does too much. >> I haven't really looked at Codehaus's xslt plugin, but maybe that's >> the way to go. >> >> Any ideas? >> >> -K, who has always gotten good suggestions from this list. >> >> >> - >> 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: Maven assembly plug-in and deploy not happening?
That was it, oops. Thank you. On Fri, Jun 27, 2008 at 1:04 PM, Jörg Schaible <[EMAIL PROTECTED]> wrote: > Hi Andrew, > > Andrew Robinson wrote: > >> The maven assembly plug-in, specifically states that it will deploy >> all the built assemblies on deploy: >> >> http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#deploy >> >> So I have my assembly plugin executions tied to the package: >> >> >> maven-assembly-plugin >> 2.2-beta-2 >> >> >> make-jar >> package >> >> assembly > > > Use the attach goal instead. > > >> >> >> > src/main/assembly/jar/ >> >> >> mypackage.Launcher >> >> >> >> >> >> make-assembly >> package >> >> assembly >> >> >> > src/main/assembly/package/ >> >> >> >> >> >> Now when I run mvn:deploy, it does not upload my assemblies, only my >> project output (jar). Do I need a different version of a plugin or >> maven or something, or is the assembly plugin FAQ wrong? > > - Jörg > > > - > 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]
Maven assembly plug-in and deploy not happening?
The maven assembly plug-in, specifically states that it will deploy all the built assemblies on deploy: http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#deploy So I have my assembly plugin executions tied to the package: maven-assembly-plugin 2.2-beta-2 make-jar package assembly src/main/assembly/jar/ mypackage.Launcher make-assembly package assembly src/main/assembly/package/ Now when I run mvn:deploy, it does not upload my assemblies, only my project output (jar). Do I need a different version of a plugin or maven or something, or is the assembly plugin FAQ wrong? mvn -version Maven version: 2.0.7 Java version: 1.5.0_15 OS name: "linux" version: "2.6.24-19-generic" arch: "i386" Thanks, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn release plugin and platform specific executable jars
Okay, found a solution. I have 4 jar assembly descriptors that make a jar with all the unpacked dependencies, then I have 4 "package" assembly descriptors to bundle it all in a tar or zip. This way I have no class path in my manifest to bother with since the jars are all self-contained. -Andrew On Thu, Jun 26, 2008 at 5:35 PM, Andrew Robinson <[EMAIL PROTECTED]> wrote: > I am deploying a maven application with 4 different packages (4 > assemblies). Each are the same except for one jar (SWT) that is > native. I have had to resort to 4 different executions of maven to > package them, one execution per profile. This is so that I can change > the classpath per execution to pull in the correct SWT jar and have > the jar plugin add it to the jar classpath manifest. I then am using > the assembly plugin to generate tar.bz2 or zip files with my batch > file or shell scripts as well as all the dependent jars. > > This is working except I don't know how to get release:perform to > work. I would like to have the scenario where I could generate the 4 > assemblies, tie in a plugin to upload the assemblies all during the > release, so that the are generated with the correct version number. It > seems, correct me if I am wrong, that my working copy is not updated > to the releasing build until during release:perform. The problem is > that I cannot create the 4 assemblies with one maven target. > > How can I accomplish this? Do I have to create my own custom plugin? > > Overview: > > Prepare the release > Generate the 4 assemblies each with a jar with a different classpath / > dependencies using the release tag > Release the 4 assemblies on the tag and upload them using ssh to my server > Deploy the new site using the same tag > Resume work on the new tag > > Advice is greatly appreciated. > > -Andrew > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Append to classpath for manifest manually?
Related to my previous post http://www.nabble.com/mvn-release-plugin-and-platform-specific-executable-jars-td18145554.html, I am wondering if it is possible to manually append a jar to the classpath of the manifest in the archive. If this is possible, I could manually add an swt jar to the classpath of my executable jar when the assembly is being created for each native platform I am releasing to. Or is there some other way that I can append to the classpath the correct SWT jar so that it is run. Java seems to ignore the -cp argument when -jar is used. I don't wish to have to use a custom class loader as that seems like a bad hack around a maven limitation (if one exists). Thanks, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mvn release plugin and platform specific executable jars
I am deploying a maven application with 4 different packages (4 assemblies). Each are the same except for one jar (SWT) that is native. I have had to resort to 4 different executions of maven to package them, one execution per profile. This is so that I can change the classpath per execution to pull in the correct SWT jar and have the jar plugin add it to the jar classpath manifest. I then am using the assembly plugin to generate tar.bz2 or zip files with my batch file or shell scripts as well as all the dependent jars. This is working except I don't know how to get release:perform to work. I would like to have the scenario where I could generate the 4 assemblies, tie in a plugin to upload the assemblies all during the release, so that the are generated with the correct version number. It seems, correct me if I am wrong, that my working copy is not updated to the releasing build until during release:perform. The problem is that I cannot create the 4 assemblies with one maven target. How can I accomplish this? Do I have to create my own custom plugin? Overview: Prepare the release Generate the 4 assemblies each with a jar with a different classpath / dependencies using the release tag Release the 4 assemblies on the tag and upload them using ssh to my server Deploy the new site using the same tag Resume work on the new tag Advice is greatly appreciated. -Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deploying SWT zipped app for 4 platforms
I am trying to determine how to bundle my SWT application to release on windows, linux, linux-amd64 and macosx. I already have 4 profiles that have the correct dependencies for each platform. What I want to do is tie this into the assembly plugin and the release plugin. This is how I can have one platform: mvn release:prepare mvn -DnoNative -Pwindows package mvn release:perform That releases just my main jar file and creates the assembly. But I am wondering how to be able to deploy the built assembly to a server for each platform Sample profile: windows windows !noNative org.eclipse swt-win32 ${eclipse.version} So my questions are: 1) Do I have to run package for each platform profile I have, or is there a way to zip them all up in one mvn execution? 2) How can I release the assembly (not just the main jar output) to a server folder? 2a) Would this be supported by the maven release plugin? 2b) or is this the domain of the wagon or similar plugin? Thank you, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SURVEY] How does your team retrieve artifacts?
[X ] Our team uses HTTP to retrieve our artifacts - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Output to console and file at the same time?
Use tee (linux command): mvn install | tee myfile.log If you are on windows, I'm sure there is a port, or at least it would work with cygwin. -Andrew On Tue, May 13, 2008 at 7:41 AM, Mick Knutson <[EMAIL PROTECTED]> wrote: > Is there a way I can get the output to the console and a file on the same > run? > > -- > > --- > Thank You… > > Mick Knutson > BASE Logic, inc. > > Website: http://www.baselogic.com > Blog: http://www.baselogic.com/blog > BLiNC Magazine: http://www.blincmagazine.com > Linked IN: http://www.linkedin.com/in/mickknutson > DJ Mick: http://www.djmick.com > MySpace: http://www.myspace.com/mickknutson > Tahoe: http://tahoe.baselogic.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]
Customization during custom archetype execution?
I have never written an archetype, so please excuse my ignorance. I would like to make a dynamic archetype. What I mean by this is to be able to have it ask users (via command prompts or just via system properties if that is not possible) what they want and be able to change the archetype on the fly. What I was envisioning: mvn archetype:create \ -DarchetypeGroupId=org.apache.myfaces.buildtools \ -DarchetypeArtifactId=myfaces-archetype-dynamic \ -DarchetypeVersion=1.0 \ -DgroupId= \ -DartifactId= Hello user, please choose a JSF implementation: 1. Mojarra 2. MyFaces Include Tomahawk? (y/N): Choose a renderkit: 1. Core 2. Tobago 3. Trinidad Choose a view handler: 1. JSP 2. Facelets Choose a data provider framework: 1. None 2. Seam 3. Orchestra etc. Is there any way to do this with the achetype plugin or do I have to write my own Maven Plugin that works like the archetype plugin that I am able to run custom Java during execution? If I can write out a base structure and then have a way to run a custom mojo after the archetype is run to be able to add resources and modify the pom.xml, that would probably work as well? Any advice? Thanks, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: when will maven 2.0.9 be officially released?
Will do, if I can get some more time. If so, I will open a new related bug or attempt to reopen one if I can pinpoint where in the source it goes wrong. Thanks On Sun, Mar 2, 2008 at 1:40 PM, Brett Porter <[EMAIL PROTECTED]> wrote: > I agree with Wendy. > > You could also whip up a test case using these instructions: > http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test > as it'll give you a head start on being included in a release. > > - Brett > > > > On 03/03/2008, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > On Sun, Mar 2, 2008 at 1:28 PM, Andrew Robinson > > > > <[EMAIL PROTECTED]> wrote: > > > > > No, 2.0.7 and 2.0.8 both do not work with JDK 1.6 because of this bug. > > > 2.1 fixed the problem. The earlier releases ran plugins and plugin > > > executions in random order due to improper use of HashMap. > > > > > > It is really easy to reproduce the problem. I had 3 executions of the > > > maven SQL plugin and they ran out of order in JDK 1.6 and are fine in > > > 2.1. JDK 1.5 worked fine as well, so it definitely seems like it was a > > > collections use bug. > > > > > > Perhaps MNG-2784 was only a partial fix? > > > > > > No idea, but it looks like all the related issues are closed. It's > > likely nothing further will happen unless an issue gets reopened or a > > new issue is raised. (It's also possible there's a technical reason > > the fix for 2.1 can't be backported to 2.0.) > > > > Have you tried 2.0.9-SNAPSHOT? If you can't find an open issue that > > describes the problem you're still having with 2.0.x, I'd open > > another. Worst case, it might get closed as WONTFIX with an > > explanation... > > > > > > -- > > > > Wendy > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > > Brett Porter > Blog: http://blogs.exist.com/bporter/ > > - > > > 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: when will maven 2.0.9 be officially released?
No, 2.0.7 and 2.0.8 both do not work with JDK 1.6 because of this bug. 2.1 fixed the problem. The earlier releases ran plugins and plugin executions in random order due to improper use of HashMap. It is really easy to reproduce the problem. I had 3 executions of the maven SQL plugin and they ran out of order in JDK 1.6 and are fine in 2.1. JDK 1.5 worked fine as well, so it definitely seems like it was a collections use bug. Perhaps MNG-2784 was only a partial fix? -Andrew On Sun, Mar 2, 2008 at 1:19 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On Sun, Mar 2, 2008 at 12:54 PM, Andrew Robinson > <[EMAIL PROTECTED]> wrote: > > Can the fix for http://jira.codehaus.org/browse/MNG-2258 be put in > > 2.0.9? This is a blocking issue for my environment and forces me to > > use 2.1-SNAPSHOT. > > What version were you using before you switched to 2.1? > > The issue you mentioned was closed as a duplicate. It's difficult to > tell with all the links, but MNG-2784 says it was fixed in 2.0.7. > > http://jira.codehaus.org/browse/MNG-2784 > > -- > Wendy > > > > - > 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: when will maven 2.0.9 be officially released?
Can the fix for http://jira.codehaus.org/browse/MNG-2258 be put in 2.0.9? This is a blocking issue for my environment and forces me to use 2.1-SNAPSHOT. Thanks, Andrew On Sun, Mar 2, 2008 at 6:09 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > End of next week is pretty much a certaint no. My personal goal is to > have the vote out by the end of the week though. We like to let the > Maven core release candidates be available for ~ a week before we shove > it out. > > > > -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Friday, February 29, 2008 7:16 PM > To: Maven Users List > Subject: Re: when will maven 2.0.9 be officially released? > > Not for certain, but both I and Brian have said we were going to do > some issues so there's a good chance. > > If you are interested in looking into any of the scheduled issues > (particularly providing test cases) that can help speed things up a > lot. > > Cheers, > Brett > > On 01/03/2008, Ryan H. <[EMAIL PROTECTED]> wrote: > > Do you know if it'll be released by end of next week? > > > > > > On 2/29/08, Brett Porter <[EMAIL PROTECTED]> wrote: > > > There's not too many issues left in the roadmap, so I would say in > the > > > next couple of weeks. I'm trying to plow through those before > adding > > > some newer things. > > > > > > - Brett > > > > > > On 01/03/2008, Paul Benedict <[EMAIL PROTECTED]> wrote: > > > > 2.0.9 is a very exciting release, imo. Perhaps on par with 2.0.4 > > > > > > > > > > > > On Fri, Feb 29, 2008 at 10:46 AM, Ryan H. <[EMAIL PROTECTED]> > wrote: > > > > > > > > > Does anyone know when maven 2.0.9 will be offcially released? > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > -- > > > Brett Porter > > > Blog: http://blogs.exist.com/bporter/ > > > > > > > - > > > 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] > > > > > > > -- > Brett Porter > Blog: http://blogs.exist.com/bporter/ > > - > 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: The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist
Yup, it doesn't exist, it is not an apache plugin, so has to be qualified: org.mortbay.jetty maven-jetty-plugin 6.1.7 -Andrew On Thu, Feb 28, 2008 at 8:32 AM, Neo Anderson <[EMAIL PROTECTED]> wrote: > I follow the http://appfuse.org/display/APF/AppFuse+QuickStart to practise to > use the maven. > > Then I encounter a problem saying 'The plugin > 'org.apache.maven.plugins:maven-jetty-plugin' does not exist' when issuing > command 'maven jetty:run-war' > > I checked the archive - http://www.mail-archive.com/[EMAIL > PROTECTED]/msg02587.html, but it seems no use. Either issuing command mvn -U > or mvn -cpu does not help to run the jetty. How can I install this plugin? > > Thank you very much. > > > > > > > > > > __ > Sent from Yahoo! Mail. > A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.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 2.0.8 bugs with JDK 1.6 and the Jetty Plug-In
BTW - is maven 2.1 (SNAPSHOT) considered relatively stable at the moment? I am considering using it now to get around my JDK 1.6 issues. My projects are relatively simple. I will give it a try, but wanted to know if I should expect any major issues. On Feb 17, 2008 10:27 PM, Andrew Robinson <[EMAIL PROTECTED]> wrote: > Maven doesn't work for me with JDK 1.6 due to Hash* usage so that > ordering of plugins and other items is no longer possible. Jetty has > no JVM property so it is not possible to run maven in JDK 1.5 and > Jetty in JDK 1.6. > > Since it seems like maven 2.1 is not going to be released soon (or is > it coming soon?), are there any hopes of getting MNG-2258 fixed soon > or working around the bug without waiting for 2.1? Without the fix > Jetty in 1.6 is not possible it seems. > > Thanks for any help, > Andrew > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven 2.0.8 bugs with JDK 1.6 and the Jetty Plug-In
Maven doesn't work for me with JDK 1.6 due to Hash* usage so that ordering of plugins and other items is no longer possible. Jetty has no JVM property so it is not possible to run maven in JDK 1.5 and Jetty in JDK 1.6. Since it seems like maven 2.1 is not going to be released soon (or is it coming soon?), are there any hopes of getting MNG-2258 fixed soon or working around the bug without waiting for 2.1? Without the fix Jetty in 1.6 is not possible it seems. Thanks for any help, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Use a custom reporter with testng and surefire?
I have the following in my pom: maven-surefire-plugin 2.4-SNAPSHOT once false true ${project.build.directory} **/*Test.java listener testing.TestNGListener reporter testing.TestNGReporter I am using TestNG 5.6 The listener is getting used, but the reporter is not. Is there some other way of setting a custom reporter with surefire & TestNG? Thanks, Andrew
Re: surefire, junit logs, and forking
Is the log output appearing in TEST-TestSuite.xml or only in the output? On Jan 3, 2008 11:13 PM, noon <[EMAIL PROTECTED]> wrote: > > I wasn't quite sure what you were asking, but I got my logging working > properly with Maven test by adding following configuration to pom.xml. > > >maven-surefire-plugin >2.2 > >false >true >pertest > > >log4j.configuration > > file:${basedir}/src/test/resources/log4j.properties > > > > > > By this I have differend log4j settings with Junit tests and development. > -- > View this message in context: > http://www.nabble.com/surefire%2C-junit-logs%2C-and-forking-tp14599065s177p14611471.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: surefire, junit logs, and forking
http://wiki.apache.org/logging-log4j/UsefulCode Look for "Configuring Log4J For Testing With Maven" Good luck getting the logs into the test xml files though, that is what doesn't work for me -Andrew On Jan 3, 2008 8:32 AM, Adam Fisk <[EMAIL PROTECTED]> wrote: > OK, anyone know what the deal is with surefire, logs, and forking? I > have my log4j.properties files in src/test/resources and > src/main/resources. For tests, my changes to log files do nothing > unless I set "never" in my surefire plugin > config. Even then, the file in src/main/resources overrides my test > resources file *when running tests*. > > Anyone know how to just get test logs working with surefire without > disabling forking? I'm running these on multiple systems and seeing > the same thing everywhere -- maven 2.0.6, 2.0.7, Linux, OS X, etc. > > Thanks very much. > > -Adam > > > -- > http://www.littleshoot.org > Open Source, Open Standards, Open Data > > - > 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 configure the location of "settings.xml"?
assuming bash, add this to your .bashrc (substitute mvn absolute path as needed): alias mvn="/usr/bin/mvn -s $*" If you are using windows or not using bash you can create a bat file or a mvn shell script that occurs earlier in your PATH so that it gets picked up first. just make sure that the mvn in your file is fully qualified or else you get a nice infinite loop. -Andrew On Jan 2, 2008 8:19 AM, Thomas Chang <[EMAIL PROTECTED]> wrote: > Thanks for the reply. But I think this way is a little bit complecated since > everytime you run mvn you have to type the alternate path. > > > ** > you can use mvn -s < Alternate path for the user settings file > > > Erez. > > On Jan 2, 2008 5:05 PM, Thomas Chang <[EMAIL PROTECTED]> wrote: > > > Hi all, > > > > Normally the "settings.xml" is located under /m2_home/conf. Is it > > possible to move this file anywhere for example /myproject/conf? If > yes, > > how? > > > > Regards > > > > Thomas > > > > > > - > Ihre erste Baustelle? Wissenswertes für Bastler und Hobby Handwerker. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Getting useful logging from surefire and testng
It is in src/test/resources. It is getting picked up since the logging is changing when I change values in it. Either way, my logs are being logged to the System.out but not appearing it the system out element in the TEST-TestSuite.xml, which I find odd. I would try it without forking to see if it is a classloader issue with commons logging or log4j, but unfortunately I have to fork since my code is JDK 1.6 and mvn has to run on 1.5 (due to some severe bugs with collections and depending on hashmap ordering in 2.0.8). -Andrew On Jan 2, 2008 12:46 AM, Jeff MAURY <[EMAIL PROTECTED]> wrote: > Andrew, > > where is you your test-log4j.xml file located ? Because if you use > log4j.configuration, I think it will use the current directory and not try > to load the file from the classpath. > > Jeff > > > On Jan 2, 2008 3:38 AM, Andrew Robinson <[EMAIL PROTECTED]> > wrote: > > > > I am having problems getting useful information from surefire logs. > > Plugin declaration: > > > >maven-surefire-plugin > >2.4-SNAPSHOT > > > > once > > false > > true > > once > > ${JAVA16_HOME}/bin/java > > ${project.build.directory} > > > >**/*Test.java > > > > > > > > log4j.configuration > > test-log4j.xml > > > > > > > > > > In the target/surefire-reports I have: > > > > TestSuite.txt: has the exceptions that TestNG caught, but no logging > > TestSuite-output.txt: has the full output except for what TestNG > > caught and test information > > TEST-TestSuite.xml: has all information that does not use JDK logging, > > commons logging or Log4J (has hibernate SQL, so I know it is picking > > up some of the System.out contents) > > testng-results.xml: Same as TestSuite.txt for the most part > > testng-failed.xml: this file is not for logging > > > > TEST-TestSuite.xml would be great if it held the contents of the > > logging output, but it does not for some reason. I can't find anything > > to be able to get it to be picked up in this file. I have a lot of > > test cases already and trying to sift through the full log and attempt > > to try to figure out what test method the logs are for is just not > > possible. How can I get the surefire test logs per method to contain > > the information logged by log4j? > > > > Here is my test-log4j.xml file contents: > > > > > > > > http://jakarta.apache.org/log4j/"; > > debug="false"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks, > > Andrew > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > La mélancolie c'est communiste > Tout le monde y a droit de temps en temps > La mélancolie n'est pas capitaliste > C'est même gratuit pour les perdants > La mélancolie c'est pacifiste > On ne lui rentre jamais dedans > La mélancolie oh tu sais ça existe > Elle se prend même avec des gants > La mélancolie c'est pour les syndicalistes > Il faut juste sa carte de permanent > > Miossec (2006) > > http://www.jeffmaury.com > http://riadiscuss.jeffmaury.com > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Getting useful logging from surefire and testng
I am having problems getting useful information from surefire logs. Plugin declaration: maven-surefire-plugin 2.4-SNAPSHOT once false true once ${JAVA16_HOME}/bin/java ${project.build.directory} **/*Test.java log4j.configuration test-log4j.xml In the target/surefire-reports I have: TestSuite.txt: has the exceptions that TestNG caught, but no logging TestSuite-output.txt: has the full output except for what TestNG caught and test information TEST-TestSuite.xml: has all information that does not use JDK logging, commons logging or Log4J (has hibernate SQL, so I know it is picking up some of the System.out contents) testng-results.xml: Same as TestSuite.txt for the most part testng-failed.xml: this file is not for logging TEST-TestSuite.xml would be great if it held the contents of the logging output, but it does not for some reason. I can't find anything to be able to get it to be picked up in this file. I have a lot of test cases already and trying to sift through the full log and attempt to try to figure out what test method the logs are for is just not possible. How can I get the surefire test logs per method to contain the information logged by log4j? Here is my test-log4j.xml file contents: http://jakarta.apache.org/log4j/"; debug="false"> Thanks, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: version in dependency is needed
> booking-ejb ... > booking-web Your artifactIds do not match - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: what is ?
can be used to set common attributes for a dep, like exclusions, version etc. So: Parent P: something something 1.0.0 Child A & C: something something Child B doesn't use something Now I can change the version for something for both A and C in one place. Basically you want this if not all your child projects use a dependency. -Andrew On Dec 21, 2007 11:33 AM, <[EMAIL PROTECTED]> wrote: > Say I have parent pom called A and child pom called B. I specified > element for B inside A and also > specified element for A inside B. Now I dont understand I > would have to declare element in A. Say if I > have B, C, D as child modules and B, C, D all 3 depend on junit then > can I declare junit as dependency in A using element > instead and in that B, C, D inherit that > instead of each B, C, D declaring the dependency. If so > in what cases do I use . > > I read the online documentation available at maven site but the > documentation section is not clear to me. Can > anyone please explain with an example. > > Thank you. > > - > 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: Don't kill the messenger
Sorry, it looks like the settings.xml that my company has us use has an update policy of always. Guess that conflicts with offline. I retract any agreement I had with that blog :) -Andrew On Dec 20, 2007 4:29 PM, Andrew Robinson <[EMAIL PROTECTED]> wrote: > Offline mode breaks when there are snapshots: > > > mvn -o install > > [INFO] Failed to resolve artifact. > > GroupId: some-group > ArtifactId: some-artifact > Version: 1.0-SNAPSHOT > > Reason: System is offline. > > some-group:some-artifact:pom:1.0-SNAPSHOT > > > > NOTE: Maven is executing in offline mode. Any artifacts not already in > your local > repository will be inaccessible. > > > It *should* work, but doesn't. Maybe I am missing something? > > > > On Dec 20, 2007 2:57 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > > You could run -o (offline) and then leave it off when you want to > > check for snapshot updates. > > > > Wayne > > > > > > On 12/20/07, Andrew Robinson <[EMAIL PROTECTED]> wrote: > > > I don't agree with most of the post, but he does have a point about > > > resolving dependencies during every build. > > > > > > On one of my projects, I am using several snapshots due to needing bug > > > fixes. I really wish I could turn off snapshot checking until I > > > specifically ask for it to check. Like a "maven.snapshot.skip" flag. > > > > > > -Andrew > > > > > > On Dec 20, 2007 2:38 PM, Mark Struberg <[EMAIL PROTECTED]> wrote: > > > > This must obviously be a guy who never had a build with more than one > > > > single module. So he never > > > > learned that it is NOT a good idea to keep all dependencies in every > > > > single module ;) > > > > > > > > Additionally this guy does not know about maven-proxy and the ability > > > > to backup all artifacts you > > > > need for the whole company. > > > > > > > > So for me, I can simply ignore his personal opinion :) > > > > > > > > LieGrü, > > > > strub > > > > > > > > --- Borut BolÄ ina <[EMAIL PROTECTED]> schrieb: > > > > > > > > > Anybody saw this post? > > > > > > > > > > http://fishbowl.pastiche.org/ > > > > > > > > > > Unfortunately the author, Charles Miller <[EMAIL PROTECTED]>, disabled > > > > > the comments to prevent spam. Hmmm. > > > > > > > > > > > > > > > > Heute schon einen Blick in die Zukunft von E-Mails wagen? > > > > www.yahoo.de/mail > > > > > > > > - > > > > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Don't kill the messenger
Offline mode breaks when there are snapshots: > mvn -o install [INFO] Failed to resolve artifact. GroupId: some-group ArtifactId: some-artifact Version: 1.0-SNAPSHOT Reason: System is offline. some-group:some-artifact:pom:1.0-SNAPSHOT NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. It *should* work, but doesn't. Maybe I am missing something? On Dec 20, 2007 2:57 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > You could run -o (offline) and then leave it off when you want to > check for snapshot updates. > > Wayne > > > On 12/20/07, Andrew Robinson <[EMAIL PROTECTED]> wrote: > > I don't agree with most of the post, but he does have a point about > > resolving dependencies during every build. > > > > On one of my projects, I am using several snapshots due to needing bug > > fixes. I really wish I could turn off snapshot checking until I > > specifically ask for it to check. Like a "maven.snapshot.skip" flag. > > > > -Andrew > > > > On Dec 20, 2007 2:38 PM, Mark Struberg <[EMAIL PROTECTED]> wrote: > > > This must obviously be a guy who never had a build with more than one > > > single module. So he never > > > learned that it is NOT a good idea to keep all dependencies in every > > > single module ;) > > > > > > Additionally this guy does not know about maven-proxy and the ability to > > > backup all artifacts you > > > need for the whole company. > > > > > > So for me, I can simply ignore his personal opinion :) > > > > > > LieGrü, > > > strub > > > > > > --- Borut BolÄ ina <[EMAIL PROTECTED]> schrieb: > > > > > > > Anybody saw this post? > > > > > > > > http://fishbowl.pastiche.org/ > > > > > > > > Unfortunately the author, Charles Miller <[EMAIL PROTECTED]>, disabled > > > > the comments to prevent spam. Hmmm. > > > > > > > > > > > > Heute schon einen Blick in die Zukunft von E-Mails wagen? > > > www.yahoo.de/mail > > > > > > - > > > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Don't kill the messenger
I don't agree with most of the post, but he does have a point about resolving dependencies during every build. On one of my projects, I am using several snapshots due to needing bug fixes. I really wish I could turn off snapshot checking until I specifically ask for it to check. Like a "maven.snapshot.skip" flag. -Andrew On Dec 20, 2007 2:38 PM, Mark Struberg <[EMAIL PROTECTED]> wrote: > This must obviously be a guy who never had a build with more than one single > module. So he never > learned that it is NOT a good idea to keep all dependencies in every single > module ;) > > Additionally this guy does not know about maven-proxy and the ability to > backup all artifacts you > need for the whole company. > > So for me, I can simply ignore his personal opinion :) > > LieGrü, > strub > > --- Borut BolÄ ina <[EMAIL PROTECTED]> schrieb: > > > Anybody saw this post? > > > > http://fishbowl.pastiche.org/ > > > > Unfortunately the author, Charles Miller <[EMAIL PROTECTED]>, disabled > > the comments to prevent spam. Hmmm. > > > > Heute schon einen Blick in die Zukunft von E-Mails wagen? > www.yahoo.de/mail > > - > 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: 2.1 download possible?
Yes that worked. I also had to downgrade the maven-sql-plugin from psql jdbc4 to jdbc3 which isn't a problem Thanks again, Andrew On Dec 20, 2007 12:56 PM, Andrew Robinson <[EMAIL PROTECTED]> wrote: > Yes it does, thank you. I'll just have to set it for the compiler and > the surefire plugin. > > > On Dec 20, 2007 12:25 PM, Tom Huybrechts <[EMAIL PROTECTED]> wrote: > > Does this help you: > > http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html > > ? > > > > > > On Dec 20, 2007 7:50 PM, Andrew Robinson <[EMAIL PROTECTED]> wrote: > > > I cannot use maven 2.0.8 due to blocker issue > > > http://jira.codehaus.org/browse/MNG-2258. > > > > > > I am running on JDK 1.6 and have SQL plugin executions in my pom. > > > Under JDK 1.6, they run out of order since the code uses Maps instead > > > of lists or a linked list map. > > > > > > My code doesn't compile on JDK 1.5 and some of my build goals fail > > > under JDK 1.6. So I am stuck without being able to use maven right > > > now. > > > > > > Can MNG-2258 be back-ported for a 2.0.8.1 release, or will 2.1 be out > > > soon (meaning in the next week or so)? > > > > > > If "no" to both of these questions, what is the best way to download, > > > or at least produce a 2.1 snapshot release? > > > > > > I am able to build > > > https://svn.apache.org/repos/asf/maven/components/trunk fine, but that > > > does not give me a runnable mvn command. Is there a WIKI for making a > > > 2.1 release that I missed? > > > > > > Thanks, > > > Andrew > > > > > > - > > > 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: 2.1 download possible?
Yes it does, thank you. I'll just have to set it for the compiler and the surefire plugin. On Dec 20, 2007 12:25 PM, Tom Huybrechts <[EMAIL PROTECTED]> wrote: > Does this help you: > http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html > ? > > > On Dec 20, 2007 7:50 PM, Andrew Robinson <[EMAIL PROTECTED]> wrote: > > I cannot use maven 2.0.8 due to blocker issue > > http://jira.codehaus.org/browse/MNG-2258. > > > > I am running on JDK 1.6 and have SQL plugin executions in my pom. > > Under JDK 1.6, they run out of order since the code uses Maps instead > > of lists or a linked list map. > > > > My code doesn't compile on JDK 1.5 and some of my build goals fail > > under JDK 1.6. So I am stuck without being able to use maven right > > now. > > > > Can MNG-2258 be back-ported for a 2.0.8.1 release, or will 2.1 be out > > soon (meaning in the next week or so)? > > > > If "no" to both of these questions, what is the best way to download, > > or at least produce a 2.1 snapshot release? > > > > I am able to build > > https://svn.apache.org/repos/asf/maven/components/trunk fine, but that > > does not give me a runnable mvn command. Is there a WIKI for making a > > 2.1 release that I missed? > > > > Thanks, > > Andrew > > > > - > > 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]
2.1 download possible?
I cannot use maven 2.0.8 due to blocker issue http://jira.codehaus.org/browse/MNG-2258. I am running on JDK 1.6 and have SQL plugin executions in my pom. Under JDK 1.6, they run out of order since the code uses Maps instead of lists or a linked list map. My code doesn't compile on JDK 1.5 and some of my build goals fail under JDK 1.6. So I am stuck without being able to use maven right now. Can MNG-2258 be back-ported for a 2.0.8.1 release, or will 2.1 be out soon (meaning in the next week or so)? If "no" to both of these questions, what is the best way to download, or at least produce a 2.1 snapshot release? I am able to build https://svn.apache.org/repos/asf/maven/components/trunk fine, but that does not give me a runnable mvn command. Is there a WIKI for making a 2.1 release that I missed? Thanks, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]