Re: [m2eclipse] Eclipse WebTools and Maven2 Publishing Failed
Publishing failed Resource /M2_REPO/commons-logging/commons-logging/1.0/commons- logging-1.0.jar does not exist. That's a WTP bug, in any version from WTP 1.0 till recent builds: https://bugs.eclipse.org/bugs/show_bug.cgi?id=116783 WTP 1.0 simply ignores external dependencies, later builds started to fail publishing if the project contains dependencies with a variable (vars are handled like phisical paths). Ony recent I/M builds are finally handling this as expected. Just grab a newer build from http://download.eclipse.org/webtools/downloads/ and you will not have problems anymore I'll release a new version of the eclipse plugin during the weekend, and I will republish the documentation with a warning on working WTP versions. fabrizio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
anyway to automate tags in release plugin?
First of all I really like the release plugin it is really useful! I have been playing around a little and I wonderif there is a way to get an automatic scm tag? Right now the release plugin asks me what tag to use, for me it would be ok if it used the version sans -SNAPSHOT of course? Can I configure it somehow? for example pom with version 1.2-SNAPSHOT should be tagged in scm as 1.2 without human assistance. Any ideas or pointers? /Konstantin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2.0.2] the skin does not exist: unable to determine the release version.
right - I took it for granted that david will still be using the new site plugin without the snapshots repo. If you revert to the old site plugin, you should be ok indeed. On 2/4/06, Brett Porter [EMAIL PROTECTED] wrote: No, the skin tag in your site descriptor will be ignored if you use the older site plugin. - Brett On 2/4/06, Arik Kfir [EMAIL PROTECTED] wrote: I think it will, because the skins (which are a standalone project on their own) were not released yet, and therefor are not present on the ibiblio repository. On 2/3/06, David Sag [EMAIL PROTECTED] wrote: Hi Arik your suggestion, in combination with emanuelle's suggestion fixed the problem (for today at least). I only enabled snapshots as part of a general attempt to get cobertura working. since that is pretty mucha lost cause for now, tell me, if i disable snapshots, will the presence of the skin tags in my site.xmlbreak anything? Kind regards, Dave Sag Arik Kfir [EMAIL PROTECTED] wrote on 03-02-2006 14:31:15: Hi David, You should remember that although Maven itself was released, some of the plugins (e.g. the site plugin) have not been released yet. You are currently using either a SNAPSHOT, or one of the BETA releases - all of which are subject to change as they are still being written and implemented. As for your problem - if the above solution does not work, try adding this (in addition to what Emmanuel specified above) to your site.xml file: skin groupIdorg.apache.maven.skins/groupId artifactIdmaven-stylus-skin/artifactId version1.0-SNAPSHOT/version /skin Best regards (and good luck :P) Arik. On 2/3/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: You use the snapshot version of site plugin, right? Add this in your pom : repositories repository releases enabledfalse/enabled /releases idapache.snapshots/id nameApache Development Repository/name urlhttp://cvs.apache.org/maven-snapshot-repository/url /repository /repositories Emmanuel David Sag a écrit : Today I got a new error when building the site for my project. the skin does not exist: unable to determine the release version. WTF? I've never seen this error before. Is it just me, or does the new found brittle nature of builds scare anyone else? It's truly scary to go home leaving a project that builds fine, and come in in the morning to discover that now it doesn't. Kind regards, Dave Sag - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Regards, _ Arik Kfir[EMAIL PROTECTED] -- Regards, _ Arik Kfir[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Regards, _ Arik Kfir[EMAIL PROTECTED]
Re: dependency typewar/type not working
Why do you need to add a war as dependency? If i's only to get all dependencies, set the dependency type to pom. Emmanuel Jason Chaffee a écrit : If I try to add a dependency of type war to my pom, I get the following error: [ERROR] FATAL ERROR [INFO] - --- [INFO] Error building POM (may not be this project's POM). Project ID: com.tvworks.tva.packager:packager-webapp POM Location: C:\workspace\packager\packager\webapp\pom.xml Validation Messages: [0] 'dependencies.dependency.version' is missing for metatv-common-assets:m etatv-common-assets Reason: Failed to validate POM [INFO] - --- [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Failed to validate POM at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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: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.project.InvalidProjectModelException: Failed to vali date POM at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLog ic(DefaultMavenProjectBuilder.java:781) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave nProjectBuilder.java:631) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi le(DefaultMavenProjectBuilder.java:303) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave nProjectBuilder.java:274) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) ... 11 more - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Best practice for choosing a groupId?
Yes. I use edu.ku.middleware for my team's projects in our local repository. -- Kathryn Huxtable Middleware Architect Core Middleware Information Technology, a division of Information Services The University of Kansas On 2/3/06 10:59 AM, Mike Perham [EMAIL PROTECTED] wrote: The old naming practices are used for compatability with existing POMs. I think your suggestion is an excellent one if we were to import the commons jars now. For instance, new versions of spring and hibernate are going in org.springframework and org.hibernate respectively. If your module is going to be publically published I would suggest using your domain name, just like you do with packages. -Original Message- From: KC Baltz [mailto:[EMAIL PROTECTED] Sent: Friday, February 03, 2006 10:50 AM To: users@maven.apache.org Subject: Best practice for choosing a groupId? Are there any guidelines for choosing a groupId for a project? It seems like there are several techniques on ibiblio and I think some of it has historical motivation. For example, the Jakarta Commons projects all seem to use a groupId that matches artifactId. So you end up with commons-util/commons-util. I would have thought the groupId would have been org.apache.jakarta with artifactId commons-util. The other question is: does the choice of groupId really matter? Does it affect anything beyond helping people locate a dependency in the repository? K.C. - 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: [m2eclipse] Eclipse WebTools and Maven2 Publishing Failed
Hi Fabrizio, On 2/4/06, Fabrizio Giustina [EMAIL PROTECTED] wrote: Publishing failed Resource /M2_REPO/commons-logging/commons-logging/1.0/commons- logging-1.0.jar does not exist. That's a WTP bug, in any version from WTP 1.0 till recent builds: https://bugs.eclipse.org/bugs/show_bug.cgi?id=116783 Thanks so much for the clarification! WTP 1.0 simply ignores external dependencies, later builds started to fail publishing if the project contains dependencies with a variable (vars are handled like phisical paths). Ony recent I/M builds are finally handling this as expected. Just grab a newer build from http://download.eclipse.org/webtools/downloads/ and you will not have problems anymore Okay, great! My environment uses Eclipse 3.2M4, WTP 1.5M4, M2 Eclipse plugin 0.0.4. Is this also fixed on the Eclipse 3.2 code stream? I'll release a new version of the eclipse plugin during the weekend, and I will republish the documentation with a warning on working WTP versions. Good idea, that will help to prevent users from thinking the problem is with the M2 Eclipse plugin. Kind Regards, John Fallows. -- http://apress.com/book/bookDisplay.html?bID=10044 Author: Pro JSF and Ajax: Building Rich Internet Components, Apress
Re: [M2] release plugin using CVS with sourceforge
Thanks, I'm convinced its a cvs/ssh setup problem. I've uploaded my public key to SF, but I can't commit from cvs commandline without entering a password. The frustrating thing is that there is no feedback - i.e. no prompt for the password - it just appears to hang. But anyway, its not a maven thing so at least I know how to attack the problem now. Thanks. --- Emmanuel Venisse [EMAIL PROTECTED] wrote: Do you use public/private keys for your connection to sourceforge cvs? If you have a passphrase, you must start a ssh agent so password won't be necessary. But i'm not sure it's the pb because you don't have a message in log. Emmanuel Paul Rule a écrit : Hi, Has anyone been using the Maven2 release plugin with CVS sourceforge? I'm having a hard time trying to get it going - it may not be a maven problem but an SSH or some other set up problem. It gets as far as trying to check in pom.xml after it's updated the version - then it freezes which I think is because it needs the password - but there is no prompt. [DEBUG] (f) resume = true [DEBUG] (f) settings = [EMAIL PROTECTED] [DEBUG] (f) tagBase = ../tags [DEBUG] (f) urlScm = scm:cvs:ext:[EMAIL PROTECTED]:/cvsroot/seleniumas sist:SeleniumAssist [DEBUG] -- end configuration -- [INFO] [release:prepare] [INFO] What tag name should be used? v042 [INFO] Verifying there are no local modifications ... [INFO] Checking lineage for snapshots ... [INFO] Checking dependencies for snapshots ... [INFO] Checking plugins for snapshots ... [INFO] What is the release version for 'net.sf.seleniumassist:seleniumassist'? [0.4.2] [INFO] Checking in modified POMs Can anyone point me in the right direction?? Thanks. http://softwarepr.wikispaces.com/ http://toolinstaller.sourceforge.net/ http://seleniumassist.sourceforge.net/ Do you Yahoo!? Yahoo! News: Get the latest news via video today! http://au.news.yahoo.com/video/ - 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] http://softwarepr.wikispaces.com/ http://toolinstaller.sourceforge.net/ http://seleniumassist.sourceforge.net/ Do you Yahoo!? Take your Mail with you - get Yahoo! Mail on your mobile http://au.mobile.yahoo.com/mweb/index.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
best place to put the username??
Hi people, I'm very new to maven 2, but I've been a maven 1.0 user for a time. I've read all the theory about profiles, which brings to me a question: What is the best place to put my username and password for the maven-scm-plugin. Perhaps the pom.xml is not the best place (In the plugin configuration) because, for security reasons, each developer might have his own user. Then, I think of configuring this plugin in the settings.xml. but I can't :( Then it think of creating a profile (named default), mark it as the activeProfile and then define a property called username. Finally in the plugin configuration, use the property. What do you think? It's a bit twisted, isn't it? Hoping from hearing from you soon Best Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] webapp archetype resources directory seems out of place
when I create a project with: mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-webapp -DarchetypeArtifactId=maven-archetype-webapp the directory structure is: my-webapp/ |-- pom.xml `-- src `-- main |-- resources `-- webapp |-- WEB-INF | `-- web.xml `-- index.jsp It seems to me that resources is on the outside of webapp b/c the webapp directory is the exploded format for the war. This makes sense, but I'm wondering if the resources directory can also be accessed if I create a my-webapp/src/main/java directory. This seems to be out of place from the standard location, which would be my-webapp/src/main/java/resources. The main reason I ask this is because I would like to have one resources directory that both test and webapp could use. I'm using spring and I would like to have only one set of xml config files for the test and webapp, but I don't really want to break the standard. Also, if I have to break the standard, then what would be the best way of doing it? thanks in advance, Mike
Re: What scope is like 'provided' and 'test' together?
Lee, Have you tried using the exclusions that are available within the dependency declarations? If this webservices.jar is needed in a project (say project-a) which is included within an ear (say ear-project), you would define the following dependency within the ear-project pom: dependency groupIdwhatever/groupId artifactIdproject-a/artifactId version1.0/version scopecompile/scope exclusions exclusion groupIdwhatever/groupId artifactIdwebservices/artifactId /exclusion /exclusions /dependency With this approach, you could use a compile scoped dependency but not have it included in the ear. Hope that helps, David On 2/3/06, Lee Meador [EMAIL PROTECTED] wrote: I have a jar (webservices.jar) that I need for these things: 1) Compile main source. 2) Run tests in projects that are dependant on this one. But not for running the main source since that will run in the ejb container. scopeprovided/scope doesn't work because the jar isn't available for the tests in the dependent projects which need to instantiate a class from the jar but not to call it. scopecompile/scope doesn't work because the jar ends up inside the ear scopetest/scope doesn't work because the main code doesn't compile. Am I looking at this wrong somehow? The one solution I have found is to put it as provided in this project and put it as 'test in another project that runs tests that need classes. (I use the term project to mean a think with a POM of its own.) The problems with this are: 1) I can't run any such tests in the same project. (I can live with this.) 2) I have to put the dependency in the other project even though it is only needed when running the test that references this project. That seems wrong in some way. Any ideas? -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Wim Peeters/Belgium/IBM is out of the office.
I will be out of the office starting 05-02-2006 and will not return until 13-02-2006. I will respond to your message when I return. In case of urgency contact Jean-Christophe Clare ([EMAIL PROTECTED]), Maes Dirk ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] parent pom
modules module pomFilepom_jar.xml/pomFile /module ... /modules Personally, I think this should be allowed... +1 -Original Message- From: Frank Russo [mailto:[EMAIL PROTECTED] Sent: Friday, February 03, 2006 8:51 AM To: Maven Users List Subject: RE: [m2] parent pom I guess I don't have a choice, but the issue is that there are other requirements to share smaller parts of the api to other projects. For instance, there are some projects that need a jar of a specific package from my project. For me to make that a separate module, I'd have to separate that package out, which would then split the code base. So I'd rather not do that. It just seems to me that the maven builders made a special case to run a build from a pom that is not named pom.xml, eg pom_jar.xml, by passing it with a -f option, then why can't the multi project setup be automated by doing something like this in the parent: modules module pomFilepom_jar.xml/pomFile /module ... /modules Personally, I think this should be allowed... Frank Russo Senior Developer FX Alliance, LLC -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Friday, February 03, 2006 8:19 AM To: Maven Users List Subject: Re: [m2] parent pom Why do you not create 3 projects like this : root - pom.xml - jar_project -pom.xml - war_project -pom.xml In your war project, you add a dependency to your jar. Your other internal projects will use the project_jar as dependency. Emmanuel Frank Russo a écrit : Does anyone know if this is possible? Just checking in case it was missed... Frank Russo Senior Developer FX Alliance, LLC -Original Message- From: Frank Russo Sent: Tuesday, January 31, 2006 12:05 PM To: Maven Users List Subject: RE: [m2] parent pom Does anyone know if the following is doable? I have a project where I build two different artifacts off the same project base. One is a war file, which we use to deploy to a tomcat server. The other is a jar file, which is just an api snapshot of our code for other internal projects to share. The way I'm doing it now, is as follows. +- project-root | +- pom.xml | +- pom_war.xml | +- pom_jar.xml | +- src ... The pom.xml is my parent, which defines all of the shared definitions (includes repositories, dependencies, profiles, etc.) The other two reference the parent and build the appropriate artifacts. What I have been doing is build the parent, build child one, and then build child two. As noted in prior emails, there is a way to do one build and generate all artifacts, however, the examples in the docs referenced below, do not handle my scenario. My questions is, is what I want possible to do? If so, how do I configure the modules/ element in the parent? If not, is there a workaround for what I want to do, besides writing a script? A script may not be such a bad option, but it just adds something that I'll need to maintain if we want to add artifacts... Frank Russo Senior Developer FX Alliance, LLC -Original Message- From: Richard Allen [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 31, 2006 9:54 AM To: Maven Users List Subject: Re: [m2] parent pom See How do I build more than one project at once? here: http://maven.apache.org/guides/getting-started/index.html If you are using Eclipse, this can be useful: http://maven.apache.org/guides/mini/guide-ide-eclipse.html Otherwise, search the mail: http://www.nabble.com/Maven---Users-f178.html Richard Allen Frank Russo wrote: Do you or anyone else know where (if it exists) the documention is for this? The pom descriptor only shows modules/. If anyone knows how to use this, please pass along. Thanks... Frank Russo Senior Developer FX Alliance, LLC -Original Message- From: Richard Allen [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 31, 2006 8:57 AM To: Maven Users List Subject: Re: [m2] parent pom If your parent project POM lists modules, then those projects will be built when the parent is built. Richard Allen Frank Russo wrote: I have a question in regards to this. Is there a way to build the projects as a whole, as you say? As of now, I have to run maven on each individual child, and I'm not sure if there is one way to call maven to run the parent and all children at once. Does anyone know if this is doable? Frank Russo Senior Developer FX Alliance, LLC -Original Message- From: Maria Odea Ching [mailto:[EMAIL PROTECTED] Sent: Monday, January 30, 2006 10:17 PM To: Maven Users List Subject: Re: [m2] parent pom Hi Fredy, The concept of parent poms can be applied to multi-module projects wherein it provides you the priviledge of building your modules individually or as a whole (project). You need to define your parent pom in your project's root
RE: Continuum Maven 2 not using settings.xml
Must be a linux issue then? It works ok for me on windows using the /win32 folder. -Original Message- From: Christian Mouttet [mailto:[EMAIL PROTECTED] Sent: Friday, February 03, 2006 8:56 AM To: Maven Users List Subject: Re: Continuum Maven 2 not using settings.xml Hi Brian, thank's. I've already tried this. The paths for global settings.xml and user settings.xml are plotted into the log file. But neither global nor user settings are used. I'm quite confused. Am Donnerstag, 2. Februar 2006 23:52 schrieb Brian E. Fox: Copy your settings.xml to \bin\linux\conf -Original Message- Subject: Continuum Maven 2 not using settings.xml Date: Montag, 30. Januar 2006 10:46 From: Christian Mouttet To: users@maven.apache.org Hello everybody, on my Linux machine I have jdk-1.5, maven-2.0.1 and continuum-1.0.2 installed. With adding any M2-Project I run into trouble: The configuration file settings.xml isn't used by Maven when called by Continuum. I have tried quite a lot with help of Emmanuel - thank's for that again. At last he wrote that all settings loading is done by maven api (http://jira.codehaus.org/browse/CONTINUUM-488). Here is my scenario: - user for Continuum - ~continuum/.profile: export ANT_HOME=/opt/ant export MAVEN_HOME=/opt/maven-1.0 export M2_HOME=/opt/maven-2.0.1 export JAVA_HOME=/opt/jdk1.5.0_02 export PATH=/sbin:/usr/sbin:/usr/local/sbin:/usr/local/bin:/usr/bin:\ /bin:$ANT_HOME/bin:$MAVEN_HOME/bin:$M2_HOME/bin:$JAVA_HOME/bin - ~: 12290 [Thread-1] INFO org.apache.maven.scm.manager.ScmManager - Executing: cvs -f -q update -d 12291 [Thread-1] INFO org.apache.maven.scm.manager.ScmManager - Working directory: /opt/continuum-1.0.2/bin/linux/../../apps/continuum/ working-directory/7 12291 [Thread-1] DEBUG org.apache.maven.scm.manager.ScmManager - Working directory: /opt/continuum-1.0.2/bin/linux/../../apps/continuum/ working-directory/7 ... 12291 [Thread-1] DEBUG org.apache.maven.scm.manager.ScmManager - Command line: cvs -f -q update -d 13004 [Thread-1] INFO org.apache.maven.continuum.execution.ContinuumBuildExecutor:ant - Resolved the executable 'ant' to '/opt/ant/bin/ant'. 13011 [Thread-1] INFO org.apache.maven.continuum.execution.ContinuumBuildExecutor:maven-1 - Resolved the executable 'maven' to '/opt/maven-1.0/bin/maven'. 13202 [Thread-1] DEBUG org.apache.maven.settings.MavenSettingsBuilder - Building Maven global-level settings from: '/opt/maven-2.0.1/conf/settings.xml' 13202 [Thread-1] DEBUG org.apache.maven.settings.MavenSettingsBuilder - Building Maven user-level settings from: '/home/continuum/.m2/settings.xml' 13451 [Thread-1] ERROR org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelper - Cannot build maven project from /opt/continuum-1.0.2/bin/linux/../../apps/continuum/working-directory/7 /pom . xml. ... from the specified remote repositories: central (http://repo1.maven.org/maven2) ... Caused by: java.net.UnknownHostException: repo1.maven.org - DNS for the internet is done by our proxy server. This server is configured correctly in settings.xml. Starting mvn from command line works properly. Any other ideas? Regards -chris ** Diese E-Mail wurde auf Viren ueberprueft. [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: [m2] deploy:deploy-file with source?
dan tran wrote: http://maven.apache.org/guides/introduction/introduction-to-the-pom.html indicates what maven will zip and deploy the your source if you pass in -DperformRelease=true. Give it a try. -Dan Still no go :-( No matter what I put in the pom.xml I have created for the jar, deploy-file keeps ignoring. How does my pom.xml have to look like in order to attach sources to a given jar that I want to deploy-file? -dirk On 1/30/06, dan tran [EMAIL PROTECTED] wrote: sorry, i thougth you already have the source zipped up. Perhaps you can zip it up before package phase. Also the Deploy plugin ( in svn ) now supports deploy artifact with classifier, but you still need to have the zip source thou -Dan On 1/30/06, Dirk Olmes [EMAIL PROTECTED] wrote: dan tran wrote: I'm currently deploying third party jars into our company's repository using deploy:deploy-file. I'd like to deploy source jars along with the binaries so manven's eclipse plugin can pick the source up and I can step through the code in the debugger. Does anyone know how/if that's possible? note possible due to http://jira.codehaus.org/browse/MDEPLOY-19 try build-helper-maven-plugin at mojo.codehaus.org as alternative I'm not sure I understand the benefit of the build-helper plugin. I created my own pom for the third party jar and add-source to it. Now I can create a source:jar but deploy-file keeps ignoring the generated source jar. I also tried to attach-artifact the source jar, to no avail ... -dirk -- A: Maybe because some people are too annoyed by top-posting. Q: Why do I not get an answer to my question(s)? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
