Re: exec:java problem
Tim O'Brien wrote: > > Alright, time to update this example to use a gov't feed from the US NWS. > > Thanks for letting me know. > oh sorry, i have made a mistake, the sample works fine. the failure was caused by the firewall of my network. sorry for the misleading:-(( -- View this message in context: http://www.nabble.com/exec%3Ajava-problem-tp24491018p24555373.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Source Repository Site (SVN)
Hi, is there a way to change the contents of the source-repository.html site which is usualy created by mvn site... I would like to change some information in this site... There are Overview, Web-Access, Ananymous access, Developer Access ... Many thanks in advance... Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Ant Plugin 2.2 Released
The Maven team is pleased to announce the release of the Maven Ant
Plugin, version 2.2.
This plugin generates an Ant build file from a POM. See the plugin's
site for more details:
http://maven.apache.org/plugins/maven-ant-plugin/
To use the updated plugin in your projects, you need to specify the
version in your plugin configuration:
org.apache.maven.plugins
maven-ant-plugin
2.2
Release Notes - Maven 2.x Ant Plugin - Version 2.2
** Bug
* [MANT-41] - mvn ant:ant fails with NPE when maven-javadoc-plugin
custom tag is specified in pom.xml
* [MANT-44] - Generated ant copy commands in package target point
to hard-coded local repository instead of ${maven.repo.local}
* [MANT-45] - basedir attribute of task of package target in
generated Ant build causes files to be archived twice
* [MANT-46] - mvn ant:ant throws a StringIndexOutOfBoundsException
* [MANT-47] - ant:clean should not delete build.xml
* [MANT-50] - Wrong build.classpath with reactor mode
* [MANT-51] - Configuration from plugin management is not considered
* [MANT-52] - NullPointerException when maven-javadoc-plugin
configuration defines multiple group elements within a groups list element.
** Task
* [MANT-42] - Update to p-u 1.5.4
Enjoy,
-The Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Source Repository Site (SVN)
you can completely override it by creating a source-repository.apt file Sent from my [rhymes with myPod] ;-) On 19 Jul 2009, at 14:39, Karl Heinz Marbaise wrote: Hi, is there a way to change the contents of the source-repository.html site which is usualy created by mvn site... I would like to change some information in this site... There are Overview, Web-Access, Ananymous access, Developer Access ... Many thanks in advance... Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Assembly plugin Question
Brian E. Fox wrote: > Make a new module that builds your assembly and place a dependency on > the war so that it will run last. Hey, that's a great idea! That will also allow me to separate the assembly from the rest, making is easier for other Dev's to understand. Thanks! :-) Jim C. signature.asc Description: OpenPGP digital signature
AW: Dependency missing on Windows
Thanks for the hint, Brett I'm pretty sure the buildserver uses 1.4 for compilation because a Class version error broke the build ;) But you are right, the server runs a 1.5 JDK and my machine a 1.6. So I think the build simply doesn't do what I'd expected. It seems to me, that the JDK is used for the dependency resolution. If so, this would explain the difference between my machine and the server. I will check that. Cheers, Robert > -Ursprüngliche Nachricht- > Von: Brett Randall [mailto:javabr...@gmail.com] > Gesendet: Samstag, 18. Juli 2009 01:30 > An: Maven Users List > Betreff: Re: Dependency missing on Windows > > Hi Robert, > > javax.xml.stream was added to the JDK @1.6 (6) - could it be that you > are building locally with a 1.6 JDK whereas your CI server is using 1.5 > (which I don't think covers this dependency in the JDK)? > > I know you have detailed some info contra to that, but it seems the > most > likely reason to me. Either way I'm pretty sure this dep is not in JDK > 1.4 on your server, which would explain the missing dep. Double-check > your local/remote build JDKs. > > Best > Brett > > > robert.kl...@innovations.de wrote: > > Hi, > > > > I have a strange experience with a missing dependency. The problem > > occurred when upgrading spring-ws-core to version 1.5.7. In that > version > > they changed a dependency from stax:stax-api to > > javax.xml.stream:stax-api. > > > > This change worked fine on my machine (yeah, I know) but broke the > build > > on our ci server, as the new dependency resolved to stax-api-1.0- > 2.jar > > which is built with Java 1.5 and not 1.4 (which we unfortunately must > > support). > > > > The interesting thing: when calling mvn dependency:tree on the server > > showed the dependency but it did not appear on my machine > > > > This of course would explain, why the build worked locally. > > > > Can anybody explain this difference in dependency resolution? > > > > Some details > > - The server is running Linux with Maven 2.0.9 and Java 1.5 > > - I'm using Windows XP with Maven 2.1.0 (but also tried 2.0.9 with > same > > result) and Java 1.6 > > - Same Repositories > > - Server and Windows should use Java 1.4 for building > > - It is mulit-module project > > - In the project is a transitive dependency to stax:stax-api in > version > > 1.0.1 (this version was used by spring-ws-core before the upgrade) > > > > Cheers, > > > > Robert Klaus > > Business Rules Management > > > > > - > 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
AW: Dependency missing on Windows
Hi, just for the record: I tried with JDK 1.5 on my machine and got the same dependencies. Cheers, Robert > -Ursprüngliche Nachricht- > Von: robert.kl...@innovations.de [mailto:robert.kl...@innovations.de] > Gesendet: Montag, 20. Juli 2009 08:29 > An: users@maven.apache.org > Betreff: AW: Dependency missing on Windows > > Thanks for the hint, Brett > > I'm pretty sure the buildserver uses 1.4 for compilation because a > Class version error broke the build ;) > > But you are right, the server runs a 1.5 JDK and my machine a 1.6. So I > think the build simply doesn't do what I'd expected. It seems to me, > that the JDK is used for the dependency resolution. If so, this would > explain the difference between my machine and the server. > > I will check that. > > Cheers, > > Robert > > > > -Ursprüngliche Nachricht- > > Von: Brett Randall [mailto:javabr...@gmail.com] > > Gesendet: Samstag, 18. Juli 2009 01:30 > > An: Maven Users List > > Betreff: Re: Dependency missing on Windows > > > > Hi Robert, > > > > javax.xml.stream was added to the JDK @1.6 (6) - could it be that you > > are building locally with a 1.6 JDK whereas your CI server is using > 1.5 > > (which I don't think covers this dependency in the JDK)? > > > > I know you have detailed some info contra to that, but it seems the > > most > > likely reason to me. Either way I'm pretty sure this dep is not in > JDK > > 1.4 on your server, which would explain the missing dep. Double- > check > > your local/remote build JDKs. > > > > Best > > Brett > > > > > > robert.kl...@innovations.de wrote: > > > Hi, > > > > > > I have a strange experience with a missing dependency. The problem > > > occurred when upgrading spring-ws-core to version 1.5.7. In that > > version > > > they changed a dependency from stax:stax-api to > > > javax.xml.stream:stax-api. > > > > > > This change worked fine on my machine (yeah, I know) but broke the > > build > > > on our ci server, as the new dependency resolved to stax-api-1.0- > > 2.jar > > > which is built with Java 1.5 and not 1.4 (which we unfortunately > must > > > support). > > > > > > The interesting thing: when calling mvn dependency:tree on the > server > > > showed the dependency but it did not appear on my machine > > > > > > This of course would explain, why the build worked locally. > > > > > > Can anybody explain this difference in dependency resolution? > > > > > > Some details > > > - The server is running Linux with Maven 2.0.9 and Java 1.5 > > > - I'm using Windows XP with Maven 2.1.0 (but also tried 2.0.9 with > > same > > > result) and Java 1.6 > > > - Same Repositories > > > - Server and Windows should use Java 1.4 for building > > > - It is mulit-module project > > > - In the project is a transitive dependency to stax:stax-api in > > version > > > 1.0.1 (this version was used by spring-ws-core before the upgrade) > > > > > > Cheers, > > > > > > Robert Klaus > > > Business Rules Management > > > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
