Re: Sonar with Maven: Fail to connect to database: Cannot loa d JDBC driver class 'oracle.jdbc.OracleDriver'
Sonar downloads everything it needs (jar file wise) inside the plugin and adds them to its Maven plugin classpath. If Sonar isn't doing this properly, its Sonar's fault (I have spent *way* too much time in the internals of Sonar). On Tue, Dec 10, 2013 at 11:34 AM, Omar@Gmail omarnet...@googlemail.comwrote: OK I see, so we are throwing it over the fence :) Sonar has very nice solution for it's side which is a folder under lib to hold jdbc drivers, shame Maven doesn't. Seems I have to stick with hacking the mvn script file. Thanks guys this is done with. On 9 December 2013 22:06, Robert Scholte rfscho...@apache.org wrote: I agree with David. The Sonar team should be able to help you. I had a small look at the code of the *plugin*[1], and it doesn't contain any references to JDBC drivers. Sonar probably has a trick, which reuses the Maven classpath. Anyhow, they know the trick, so they should know the solution for you. Robert [1] http://mojo.codehaus.org/sonar-maven-plugin/xref/index.html Op Mon, 09 Dec 2013 22:46:51 +0100 schreef Omar@Gmail omarnet...@googlemail.com: Thanks David, The problem is Maven side as I have clearly explained so not not sure why I should pursue this on Sonar user list. Explain to me why you still think it is a Sonar issue. On 9 December 2013 00:44, David Karr davidmichaelk...@gmail.com wrote: I suggest you pursue this on the Sonar user list, then. On Sun, Dec 8, 2013 at 11:55 AM, Omar@Gmail omarnet...@googlemail.com wrote: Thanks David, Yes Sonar on separate server. Also please see http://www.mail-archive.com/users@maven.apache.org/msg132123.html On 8 December 2013 18:31, David Karr davidmichaelk...@gmail.com wrote: I assume that your Sonar server is not the box you're running Maven on? What Sonar properties are you setting in your settings.xml? Feel free to omit the value for each if you need to. In the Sonar installation instructions there is a section titled Adding the JDBC Driver which talks about adding the Oracle JDBC driver to the SONAR installation. Have you done this? On Sat, Dec 7, 2013 at 4:33 AM, Omar@Gmail omarnet...@googlemail.com wrote: Objective: Get Maven to publish sonar results to running Sonar server Steps: - Installed and ran Sonar, accessible from browser - The back-end database is Oracle - Installed and configured Maven in settings.xml file to connect to the Oracle db - Invoked: mvn clean install -DSkipTests=true - Invoke: mvn sonar:sonar But getting following mvn sonar:sonar Fail to connect to database: Cannot load JDBC driver class 'oracle.jdbc.OracleDriver' So I need somehow to put the ojdbc6.jar on Maven classpath. Tried placing the ojdbc6.jar in /lib and lib/ext but did not help. Am I missing something here? please help. To fix this I modified *maven113home/bin/mvn*.bat at line 161 and added %MAVEN_JAVA_EXE% %MAVEN_OPTS% -classpath path/to/ojdbc6.jar;... *Which is nasty!* Please suggest a better approach. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- --- Richard Vowles, Groovy, Java, Javascript, AngularJS ph: +64275467747, google+:plus.to/Richard.Vowles http://rvowl.es/UX8Bmq
Re: NAR Maven Plugin 3.0.0 released
Agreed! Nar has reduced my C++ source code hell in the past, very glad to see it updated! On Mon, Dec 9, 2013 at 6:30 PM, Manfred Moser manf...@simpligility.comwrote: Great work and congratulations to everyone involved. manfred Hi all! On behalf of the developers working hard on the NAR plugin for Maven, it is my pleasure to announce that it is available on Maven Central now: http://search.maven.org/#artifactdetails|com.github.maven-nar|nar-maven-plugin|3.0.0|maven-plugin To use it, add this to your pom.xml: plugin groupIdcom.github.maven-nar/groupId artifactIdnar-maven-plugin/artifactId version3.0.0/version /plugin Since October 17th, 2010, the date of the last commit of Mark Donszelmann (the original author of the NAR plugin for Maven who is unfortunately unable to maintain it any longer), a lot of things happened. First of all, the plugin found a new home on GitHub: http://maven-nar.github.io/nar-maven-plugin/ with a team of developers and a mailing list/forum at https://groups.google.com/group/maven-nar a Git repository at https://github.com/maven-nar/nar-maven-plugin a bug tracker at https://github.com/maven-nar/nar-maven-plugin/issues and Frequently Asked Questions at https://github.com/maven-nar/nar-maven-plugin/wiki/Frequently_Asked_Questions Since the Git history does a fine job at listing the fine-grained changes, here is a coarse-grained list of changes: * unified Richard Kerr's, Greg Domjan's and SciJava's forks of the maven-nar-plugin (as it was formerly known) * renamed the plugin to conform with Maven's requirements * moved to a new groupId to reflect that we're on GitHub now * switch to deploy to OSS Sonatype (mirrored on Maven Central) * continuous integration testing thanks to BuildHive * merged the cpptasks-parallel code directly into nar-maven-plugin * support for MacOSX 10.9 * support for Microsoft Visual C++ resource and message compilers * support for Java 7's javah * support developing the Java part of projects using the NAR plugin in Eclipse * robust version detection of Microsoft's linkers * boat loads of bug fixes (as in: megatons of bug fixes) This would not have been possible without the tremendous support and contributions of the community. Thank you all! Ciao, Johannes Schindelin, Curtis Rueden and NAR development team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- --- Richard Vowles, Groovy, Java, Javascript, AngularJS ph: +64275467747, google+:plus.to/Richard.Vowles http://rvowl.es/UX8Bmq
Re: dependency:tree gets wrong version?
Enforcing it would be: dependency groupIdorg.codehaus.woodstox/groupId artifactIdwoodstox-core-asl/artifactId version[4.2.0]/version /dependency Note the square brackets around the version. 4.2.0 is still simply an advised version, and Maven can and will override it. With the square brackets it will fail. On Fri, Sep 20, 2013 at 4:32 AM, Ziga GREGORIC ziga.grego...@gmail.comwrote: Try enforcing version with dependencyManagement dependencies dependency groupIdorg.codehaus.woodstox/groupId artifactIdwoodstox-core-asl/artifactId version4.2.0/version /dependency /dependencies /dependencyManagement on parent level (check if this is the right artifact). Regards, Ziga Gregoric On Thu, Sep 19, 2013 at 4:17 PM, James Green james.mk.gr...@gmail.com wrote: Gotta be a simple one this! Upgraded ourselves to apache-cxf-2.7.6 and we've been getting errors since. Well-publicised solution is to find and remove any dependencies on woodstox prior to 4.2.0. So dependency:tree only shows us having 4.2.0. Yet clean build results in WEB-INF/lib having 4.1.2. On both cases we are operating at the parent module level. Any ideas how else to find this apparently stuck dependency? James -- --- Richard Vowles, Groovy, Java, Javascript, AngularJS ph: +64275467747, google+:plus.to/Richard.Vowles http://rvowl.es/UX8Bmq
Re: version range: fix version prefix + RELEASE
Start with .1 - really, its quite simple. Always start with 1.1-SNAPSHOT, 2.1-SNAPSHOT, never ever never ever use .0 Then version ranges work perfectly. On Fri, Aug 2, 2013 at 6:21 AM, Wayne Fay wayne...@gmail.com wrote: example. In theory this should be accomplished by [1.8.0,1.9.0). But due to http://jira.codehaus.org/browse/MNG-3092 http://jira.codehaus.org/browse/MNG-3092 this also includes snapshots I do not want. Is there some possibility to override the default maven dependecy resolver somehow? If you read MNG-3092 (it is long!), you'll see this is not currently possible. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- --- Richard Vowles, Grails, Groovy, Java, Javascript, AngularJS Consistency is the last refuge of the unimaginative - Oscar Wilde ph: +64275467747, google+:http://rvowl.es/UX8Bmq podcast: http://www.illegalargument.com
Re: Maven and JPA/EclipseLink Configuration...
On Wed, Jul 10, 2013 at 4:50 AM, John Patrick nhoj.patr...@gmail.comwrote: I'm working on a project that uses JPA EclipseLink, everything started of fine with Jetty for developers development and WebLogic and Oracle proper ear deployments. People still do that? Wow, thats educational in and of itself. -- --- Richard Vowles, Grails, Groovy, Java, Javascript, AngularJS Consistency is the last refuge of the unimaginative - Oscar Wilde ph: +64275467747, google+:http://rvowl.es/UX8Bmq podcast: http://www.illegalargument.com
Re: Is the maven repo damaged?
It does appear dead, http://repo1.maven.org/maven2/org/springsource/ gives a 404 Do you not have your own Nexus to protect yourself from this? On Jun 1, 2013 9:12 AM, Loyall, David david.loy...@nebraska.gov wrote: Hello. My maven installation has had some trouble downloading artifacts today. hobbes@metalbaby:~/scratch$ mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get -Dartifact=org.springsource:spring-jdbc:3.2.3.RELEASE [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Maven Stub Project (No POM) 1 [INFO] [INFO] [INFO] --- maven-dependency-plugin:2.8:get (default-cli) @ standalone-pom --- [INFO] Resolving org.springsource:spring-jdbc:jar:3.2.3.RELEASE with transitive dependencies Downloading: http://repo.maven.apache.org/maven2/org/springsource/spring-jdbc/3.2.3.RELEASE/spring-jdbc-3.2.3.RELEASE.pom [WARNING] Missing POM for org.springsource:spring-jdbc:jar:3.2.3.RELEASE Downloading: http://repo.maven.apache.org/maven2/org/springsource/spring-jdbc/3.2.3.RELEASE/spring-jdbc-3.2.3.RELEASE.jar [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 4.374s [INFO] Finished at: Fri May 31 15:54:12 CDT 2013 [INFO] Final Memory: 8M/106M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:get (default-cli) on project standalone-pom: Couldn't download artifact: Missing: [ERROR] -- [ERROR] 1) org.springsource:spring-jdbc:jar:3.2.3.RELEASE [ERROR] [ERROR] Try downloading the file manually from the project website. [ERROR] [ERROR] Then, install it using the command: [ERROR] mvn install:install-file -DgroupId=org.springsource -DartifactId=spring-jdbc -Dversion=3.2.3.RELEASE -Dpackaging=jar -Dfile=/path/to/file [ERROR] [ERROR] Alternatively, if you host your own repository you can deploy the file there: [ERROR] mvn deploy:deploy-file -DgroupId=org.springsource -DartifactId=spring-jdbc -Dversion=3.2.3.RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] [ERROR] [ERROR] Path to dependency: [ERROR] 1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 [ERROR] 2) org.springsource:spring-jdbc:jar:3.2.3.RELEASE [ERROR] [ERROR] -- [ERROR] 1 required artifact is missing. [ERROR] [ERROR] for artifact: [ERROR] org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 [ERROR] [ERROR] from the specified remote repositories: [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false) [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException I did some troubleshooting and determined that the problem is that the artifacts aren't on the repo in the place where mvn is looking for them. http://repo.maven.apache.org/maven2/org/springsource/spring-jdbc/3.2.3.RELEASE/spring-jdbc-3.2.3.RELEASE.pom == 404 I checked some other locations, too: http://repo2.maven.apache.org/maven2/org/springsource/spring-jdbc/3.2.3.RELEASE/spring-jdbc-3.2.3.RELEASE.pom == 404 http://central.maven.org/maven2/org/springsource/spring-jdbc/3.2.3.RELEASE/spring-jdbc-3.2.3.RELEASE.pom == 404 If it doesn't exist, fine, but, why does this say that the file should be in those location? http://search.maven.org/#artifactdetails%7Corg.springframework%7Cspring-jdbc%7C3.2.3.RELEASE%7Cjar Am I reading that correctly? Is it true that I should find org.springsource:spring-jdbc:3.2.3.RELEASE at one of those URLs that is 404? Or at least find it with my mvn client? These search results and direct url are the same as above, except the latter works! http://search.maven.org/#artifactdetails%7Clog4j%7Clog4j%7C1.2.17%7Cbundle http://repo2.maven.apache.org/maven2/log4j/log4j/1.2.17/log4j-1.2.17.pom I hope this helps, --Dave
Re: Is the maven repo damaged?
ha! i didnt even check that :-) checking a different repo shows its up and happy. On Jun 1, 2013 9:18 AM, Stuart McCulloch mccu...@gmail.com wrote: On 31 May 2013, at 22:04, Loyall, David wrote: Hello. My maven installation has had some trouble downloading artifacts today. hobbes@metalbaby:~/scratch$ mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get -Dartifact=org.springsource:spring-jdbc:3.2.3.RELEASE [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Maven Stub Project (No POM) 1 [INFO] [INFO] [INFO] --- maven-dependency-plugin:2.8:get (default-cli) @ standalone-pom --- [INFO] Resolving org.springsource:spring-jdbc:jar:3.2.3.RELEASE with transitive dependencies Downloading: http://repo.maven.apache.org/maven2/org/springsource/spring-jdbc/3.2.3.RELEASE/spring-jdbc-3.2.3.RELEASE.pom [WARNING] Missing POM for org.springsource:spring-jdbc:jar:3.2.3.RELEASE Downloading: http://repo.maven.apache.org/maven2/org/springsource/spring-jdbc/3.2.3.RELEASE/spring-jdbc-3.2.3.RELEASE.jar [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 4.374s [INFO] Finished at: Fri May 31 15:54:12 CDT 2013 [INFO] Final Memory: 8M/106M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:get (default-cli) on project standalone-pom: Couldn't download artifact: Missing: [ERROR] -- [ERROR] 1) org.springsource:spring-jdbc:jar:3.2.3.RELEASE [ERROR] [ERROR] Try downloading the file manually from the project website. [ERROR] [ERROR] Then, install it using the command: [ERROR] mvn install:install-file -DgroupId=org.springsource -DartifactId=spring-jdbc -Dversion=3.2.3.RELEASE -Dpackaging=jar -Dfile=/path/to/file [ERROR] [ERROR] Alternatively, if you host your own repository you can deploy the file there: [ERROR] mvn deploy:deploy-file -DgroupId=org.springsource -DartifactId=spring-jdbc -Dversion=3.2.3.RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] [ERROR] [ERROR] Path to dependency: [ERROR] 1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 [ERROR] 2) org.springsource:spring-jdbc:jar:3.2.3.RELEASE [ERROR] [ERROR] -- [ERROR] 1 required artifact is missing. [ERROR] [ERROR] for artifact: [ERROR] org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 [ERROR] [ERROR] from the specified remote repositories: [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false) [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException I did some troubleshooting and determined that the problem is that the artifacts aren't on the repo in the place where mvn is looking for them. http://repo.maven.apache.org/maven2/org/springsource/spring-jdbc/3.2.3.RELEASE/spring-jdbc-3.2.3.RELEASE.pom == 404 I checked some other locations, too: http://repo2.maven.apache.org/maven2/org/springsource/spring-jdbc/3.2.3.RELEASE/spring-jdbc-3.2.3.RELEASE.pom == 404 http://central.maven.org/maven2/org/springsource/spring-jdbc/3.2.3.RELEASE/spring-jdbc-3.2.3.RELEASE.pom == 404 If it doesn't exist, fine, but, why does this say that the file should be in those location? http://search.maven.org/#artifactdetails%7Corg.springframework%7Cspring-jdbc%7C3.2.3.RELEASE%7Cjar Am I reading that correctly? The search results say it's under org.springframework... whereas you appear to be looking under org.springsource... Is it true that I should find org.springsource:spring-jdbc:3.2.3.RELEASE at one of those URLs that is 404? Or at least find it with my mvn client? These search results and direct url are the same as above, except the latter works! http://search.maven.org/#artifactdetails%7Clog4j%7Clog4j%7C1.2.17%7Cbundle http://repo2.maven.apache.org/maven2/log4j/log4j/1.2.17/log4j-1.2.17.pom I hope this helps, --Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ERROR] OverConstrainedVersionException
If you are using version ranges, start at 1.1 or 1.1.1 otherwise for your version range you'll get 2.0.0-SNAPSHOT turning up like Curtis said. Thats a rule for our organisation, all artifacts must start at X.1-SNAPSHOT. On Sat, May 25, 2013 at 7:28 AM, proverbio proverb...@gmail.com wrote: Thanks a lot Curtis! I solved this error adding a new repo to my Nexus that has the artifact app-1.0.0.jar. Thanks again! :) -- View this message in context: http://maven.40175.n5.nabble.com/ERROR-OverConstrainedVersionException-tp5756918p5756955.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 -- --- Richard Vowles, Grails, Groovy, Java, Javascript, AngularJS Consistency is the last refuge of the unimaginative - Oscar Wilde ph: +64275467747, google+:http://rvowl.es/UX8Bmq podcast: http://www.illegalargument.com
Re: Shade plugin plus WAR overlays
what needs concatenating? there isnt much designed to be anti-modular these days. On Apr 16, 2013 6:56 PM, Mark Eggers its_toas...@yahoo.com wrote: Hi, I'm fairly new to Maven, and I'm trying to meet the following requirements. 1. A web site consisting of multiple components, some optional 2. Optional components each have some configuration files 3. If multiple optional components are present, the configuration files should be concatenated My first pass using WAR overlays and the shade plugin worked, in that the resulting site.war had all the right components. However, target/site did not contain the concatenated files created by the shade plugin. This prevented target/site being run from within an IDE. If I thought about it for a minute, that's pretty obvious since the shade plugin is executed during the package part of the lifecycle. What I came up with is the following: 1. Create a multi-module project 2. One module collects all of the components that require use of the shade plugin 3. The second module is the actual site, and depends on the collections module 4. Use the WAR plugin overlay, plus exclusions, plus the shade plugin to create an intermediate WAR in the collections module 5. Overlay that intermediate WAR on the final site This works except that I now have an extra artifact that is only used during the build. I can run target/site from the IDE (great for debugging) and site.war looks as it should. Other than the fact that this works, is this the proper Maven way? The extra artifact (an artifact of the build process as it were) feels a little odd. . . . . just my two cents /mde/ --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Shade plugin plus WAR overlays
On Wed, Apr 17, 2013 at 7:43 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hmm. I understand what ClassLoader.getResources(path) returns (just read the javadoc). However, if I have a bunch of independently developed components that are assembled as WAR overlays, then the first file in with a particular name wins. You are reading the javadoc of getResource(path) not getResources(path) note the s at the end. Stephen, I don't think you read what Mark wrote, and he is correct. The Maven WAR plugin, when it overlays, *overwrites* competing filenames with the same name. Your solution will work if they are the same name and in embedded jar files, but will not work for a war overlay. We have exactly this situation for jawr configuration files - each war overlay needs to specify jawr-artifactid.properties - then we classpath scan for /WEB-INF/jawr-*.properties and assemble them using JAWR's muultiple source capability. Mark - we use war overlays, but we have built the necessary stuff to make us productive in and outside of the IDE. We use Jetty 9 and a runnable war, not sure if that matches at all, but we have code we can give you if it helps. We will be open sourcing once we move to git but our artifacts will never be in central as we are open sourcing them to allow for students to enhance and hack on our projects. Contact me off list if you are interested and I'll send you everything. Richard -- --- Richard Vowles, Grails, Groovy, Java, Javascript, AngularJS Consistency is the last refuge of the unimaginative - Oscar Wilde ph: +64275467747, google+:http://rvowl.es/UX8Bmq podcast: http://www.illegalargument.com
adding files to the release
Is there any way to add files that get committed along with the prepare phase? I need a fully realized pom which the prepare-with-pom doesn't give me because of bugs in Aether, and our team uses Grails - which updates two files at release time to keep in sync with the pom version. I can't see any method of adding items to get committed in the release goals (not new items, but updated ones). Anyone got any ideas? Ta Richard -- --- Richard Vowles, Grails, Groovy, Java, Javascript, AngularJS Consistency is the last refuge of the unimaginative - Oscar Wilde ph: +64275467747, google+:http://rvowl.es/UX8Bmq podcast: http://www.illegalargument.com
Re: adding files to the release
Hi - I already explained why this was necessary, I'm looking for a
solution.
It looks like I'm going to have to fork the release plugin.
Richard
On Wed, Feb 20, 2013 at 9:04 AM, Baptiste MATHUS m...@batmat.net wrote:
Was answering on the phone on my previous mail.
Being a bit more speculative: it depends on what you do, but if I try to
guess:
you might have something that stores resolved props ('${project.version} in
some of your code).
If so, you want to avoid that kind of manipulation in the sources. Prefer
filtering properties file in src/main/resources and load it at runtime,
that's the standard way to go. And going the standard way with Maven will
always pay off later.
Cheers
2013/2/19 Baptiste MATHUS m...@batmat.net
Hi,
Which kind of updates are you doing exactly?
As a general rule, it'd be better to not touch files under the src
directories.
Cheers
Le 19 févr. 2013 11:04, Richard Vowles rich...@bluetrainsoftware.com
a écrit :
Is there any way to add files that get committed along with the prepare
phase?
I need a fully realized pom which the prepare-with-pom doesn't give me
because of bugs in Aether, and our team uses Grails - which updates two
files at release time to keep in sync with the pom version.
I can't see any method of adding items to get committed in the release
goals (not new items, but updated ones).
Anyone got any ideas?
Ta
Richard
--
---
Richard Vowles,
Grails, Groovy, Java, Javascript, AngularJS
Consistency is the last refuge of the unimaginative - Oscar Wilde
ph: +64275467747, google+:http://rvowl.es/UX8Bmq
podcast: http://www.illegalargument.com
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
--
---
Richard Vowles,
Grails, Groovy, Java, Javascript, AngularJS
Consistency is the last refuge of the unimaginative - Oscar Wilde
ph: +64275467747, google+:http://rvowl.es/UX8Bmq
podcast: http://www.illegalargument.com
Re: Maven 2 tree vs Maven 3 list
Ok - so is anyone actively working on it? I suspect finding what the bug is will make it easier to create a test case for it, so if no-one else has the time, I will find the time. Thanks! Richard On Wed, Feb 13, 2013 at 12:22 AM, Arnaud Héritier aherit...@gmail.comwrote: Even if I find this bug critical I think nobody had the time to study it more deeply (me the first) and for now I'm always downgrading to maven 2 and the dependency plugin 2.4 when I have to use either the tree or the list goals (which is a mess). Like you I provided some logs but I didn't succeeded to create an easy test case to create an integration test case. Aether is sadly a bug black box for many of us which explains why it's not easy to fix. - Arnaud Le 12 févr. 2013 à 08:09, Richard Vowles rich...@bluetrainsoftware.com a écrit : So do we know if they are being worked on? Is there a page somewhere that might explain where to start to find aether bugs? I remember the last time I looked and it was seriously confusing :-) Thanks for the heads up. On Feb 12, 2013 7:26 PM, Arnaud Héritier aherit...@gmail.com wrote: Yes there are some known issues already open in the dependency plugin Jira. The bug is somewhere in the dependency walker of aether. It seems that aether has the right deps but it doesn't allow plugins (I had the bug in dependency plugin but also in enforcer) to browse these deps accordingly to what it has in memory. - Arnaud Le 12 févr. 2013 à 06:55, Richard Vowles rich...@bluetrainsoftware.com a écrit : I made a bug report focused on the disappearing dependencies in Aether. http://jira.codehaus.org/browse/MNG-5433 - 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 -- --- Richard Vowles, Grails, Groovy, Java, Javascript, AngularJS Consistency is the last refuge of the unimaginative - Oscar Wilde ph: +64275467747, google+:http://rvowl.es/UX8Bmq podcast: http://www.illegalargument.com
Re: Maven proxy problem in ubuntu 12.04
Take one of those URLs and type wget http://... See if that works On Feb 13, 2013 1:14 PM, dzungdev dzung...@gmail.com wrote: Dear Hanasaki, I would like to say thanks for your detail explanation. I saw that you put the host is: firewall.domain.com but how I can get the information of username/password for it ? Actually I tried to get information of proxy via firefox by go to Edit -- Preference -- Advanced -- Network -- Settings but I saw that the current option is: use System proxy. Then I tried to check my ubuntu 12.04 to see proxy information but when I go to System setting -- network setting -- Proxy, the use mode is None. Thanks and best regards, Dzung -- View this message in context: http://maven.40175.n5.nabble.com/Maven-proxy-problem-in-ubuntu-12-04-tp5746764p5746837.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
Maven 2 tree vs Maven 3 list
Maven 3 seems to have problems with its dependency resolution. On the same project a dependency:list returns results that are different (in terms of scope and actual artifacts) that are different between the two requests. The Maven 2 one is right - there is no way that our AspectJ stuff isn't being depended on for example. Is anyone else having these kinds of problems? This is a diff of the two results diff m2 m3 16d15 com.google.protobuf:protobuf-java:jar:2.3.0:compile 18d16 com.googlecode.json-simple:json-simple:jar:1.1:compile 51c49,50 javax.mail:mail:jar:1.4.1:compile --- javax.mail:mail:jar:1.4.6:compile javax.persistence:persistence-api:jar:1.0:compile 55c54,55 javax.transaction:jta:jar:1.1:compile --- javax.servlet:servlet-api:jar:2.4:compile javax.transaction:jta:jar:1.1.0:compile 58d57 jline:jline:jar:1.0:compile 164,167c163,164 org.apache.ant:ant-junit:jar:1.8.2:compile org.apache.ant:ant-launcher:jar:1.8.2:compile org.apache.ant:ant-trax:jar:1.7.1:compile org.apache.ant:ant:jar:1.8.2:compile --- org.apache.ant:ant-launcher:jar:1.7.1:compile org.apache.ant:ant:jar:1.7.1:compile 191,194d187 org.aspectj:aspectjrt:jar:1.6.10:runtime org.aspectj:aspectjweaver:jar:1.6.10:runtime org.bouncycastle:bcpg-jdk15:jar:1.45:compile org.bouncycastle:bcprov-jdk15:jar:1.45:compile 196c189,191 org.codehaus.gant:gant_groovy1.8:jar:1.9.6:compile --- org.coconut.forkjoin:jsr166y:jar:070108:compile org.codehaus.gant:gant_groovy1.7:jar:1.9.2:compile org.codehaus.gpars:gpars:jar:0.9:compile 208d202 org.fusesource.jansi:jansi:jar:1.2.1:compile 219c213 org.grails:grails-bootstrap:jar:2.0.3:compile --- org.grails:grails-bootstrap:jar:1.3.7:compile 245c239 org.grails:grails-test:jar:2.0.3:test --- org.grails:grails-test:jar:2.0.3:compile 248c242 org.hamcrest:hamcrest-core:jar:1.1:test --- org.hamcrest:hamcrest-core:jar:1.1:compile 271c265 org.slf4j:jul-to-slf4j:jar:1.6.2:runtime --- org.slf4j:jul-to-slf4j:jar:1.6.2:compile 273c267 org.slf4j:slf4j-api:jar:1.6.1:compile --- org.slf4j:slf4j-api:jar:1.6.2:compile 278d271 org.springframework.uaa:org.springframework.uaa.client:jar:1.0.1.RELEASE:compile 311c304 xalan:serializer:jar:2.7.1:runtime --- xalan:serializer:jar:2.7.1:compile -- --- Richard Vowles, Grails, Groovy, Java, Javascript, AngularJS Consistency is the last refuge of the unimaginative - Oscar Wilde ph: +64275467747, google+:http://rvowl.es/UX8Bmq podcast: http://www.illegalargument.com
Re: Maven 2 tree vs Maven 3 list
I made a bug report focused on the disappearing dependencies in Aether. http://jira.codehaus.org/browse/MNG-5433
Re: Maven 2 tree vs Maven 3 list
So do we know if they are being worked on? Is there a page somewhere that might explain where to start to find aether bugs? I remember the last time I looked and it was seriously confusing :-) Thanks for the heads up. On Feb 12, 2013 7:26 PM, Arnaud Héritier aherit...@gmail.com wrote: Yes there are some known issues already open in the dependency plugin Jira. The bug is somewhere in the dependency walker of aether. It seems that aether has the right deps but it doesn't allow plugins (I had the bug in dependency plugin but also in enforcer) to browse these deps accordingly to what it has in memory. - Arnaud Le 12 févr. 2013 à 06:55, Richard Vowles rich...@bluetrainsoftware.com a écrit : I made a bug report focused on the disappearing dependencies in Aether. http://jira.codehaus.org/browse/MNG-5433 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: retrieve package list
release:prepare-with-pom gives you a release pom with all transitives and their versions in it. However it doesn't retain excludes and doesn't use force version notation [] so it has some problems. Its also only useful when you are releasing which is not necessarily a bad thing. On Sat, Nov 24, 2012 at 2:43 PM, Wayne Fay wayne...@gmail.com wrote: and the maven plugin would fetch and export this : org.myproject.view.main, org.myproject.view.panels.log, org.apache.log4j, org.apache.log4j.filter, Where would this be fetched from? Do you mean you want a plugin to search all the Java code and find all the imports, then write the imports out to a file? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- --- Richard Vowles, Grails, Groovy, Java, Javascript, AngularJS Consistency is the last refuge of the unimaginative - Oscar Wilde ph: +64275467747, google+:http://rvowl.es/UX8Bmq podcast: http://www.illegalargument.com
Re: Multiple Local Repositories
Use a different settings file. and configure the right dir in each one: http://jan.baresovi.cz/dr/en/maven-command-line and http://maven.apache.org/settings.html On Fri, Nov 2, 2012 at 2:14 AM, iamanandkris iamanandk...@gmail.com wrote: Hi Can we have more than one local maven repositories in a computer? So that I can use one repo for on of my projects and other for other projects? If so can some one pls give some guide lines on how to facilitate that? Thank you Anand -- View this message in context: http://maven.40175.n5.nabble.com/Multiple-Local-Repositories-tp5729020.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 -- --- Richard Vowles, Grails, Groovy, Java, Javascript, AngularJS Consistency is the last refuge of the unimaginative - Oscar Wilde ph: +64275467747, google+:http://rvowl.es/UX8Bmq podcast: http://www.illegalargument.com
Re: Twisted Versioning Question
Or, better still, stop using hibernate and save yourself a huge headache. Use Ebean or something like it. On Oct 22, 2012 5:03 AM, Wayne Fay wayne...@gmail.com wrote: currently attempting to untangle the twisted architecture behind Redhats hibernate (v3.3.0.ga) and I came upon this take a look at the main dependency for annotations version=3.3.0.ga then take a look at the core version it depends on = 3.2.1.ga Probably need to ask these Hibernate-specific questions on the Hibernate Developers list. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Version ranges not working
The composite pattern also makes exclusion very easy.
On Sep 30, 2012 3:35 PM, Michael McCallum mich...@stickycode.net wrote:
I - almost - disagree completely, I've successfully used ranges on seven
separate commercial projects. A mix of sizes from corporate to startup.
If you care at all about agility being explicit everyone is very
cumbersome, the fundamental aspect is determinism - meaning that its
obvious WHY it behaves the way it does, once you understand how maven
implements ranges its very easy to use to them to great effect.
Having said that using ranges can be dangerous hence the composition
pattern mentioned in my previous email.
When you say nail down your version do you use [1.7.1] or 1.7.1?
On Fri, Sep 28, 2012 at 11:20 AM, Baptiste MATHUS m...@batmat.net wrote:
+1.
Version ranges are basically just a bad practice in my experience. I
mostly
don't see any interest apart from being able to see a normally passing
build suddenly going rogue because you somehow had a dependency update
somewhere in the dependency tree. (I wrote something similar in that
comment
http://www.sonatype.com/people/2012/08/download-it-all-at-once-a-maven-idea/#comment-635524577
)
So, please, Maven users, don't use them. It's like having scripts inside
your pom.xml, it might seem sexy and powerful, but it's dangerous.
Nail down a version, and upgrade explicitly when you need to and/or are
ready to. You'll be very happy that way and your build'll stay green.
Cheers
2012/9/28 Stephen Connolly stephen.alan.conno...@gmail.com
Well that is a recipe for disaster. rules only make sense within the
scope
of the artifacts they apply to.
This is kind of why version ranges are next to useless from a practical
PoV
anyway
On 27 September 2012 23:05, Paul French paul.fre...@kirona.com
wrote:
I would only want the same version rules applied to all artifacts,
not
on
a per artifact basis, that would be a nightmare! I understand that
people
who produce artifacts have their own versioning rules. However we can
take
that into account in our version ranging.
Usually for 3rd party artifacts we have a very narrow version range
since
we cannot trust the producer of that artifact not to break their
current
API in later versions unless they support semantic versioning.
On 27/09/2012 22:29, Stephen Connolly wrote:
when is that class applied?
each dependency would have its own comparator, as each dependency
has
its
own versioning rules.
and then don't start on epoch's (i.e. where the versioning rules
change
from under your feet mid sequence
It's tempting... but dangerous... the closest I have come up with is
the
rulesets hack from versions-maven-plugin @ mojo... but even that has
issues... hence why I haven't pushed it further.
-Stephen
On 27 September 2012 22:19, Paul French paul.fre...@kirona.com
wrote:
Okay I see the problem.
How about allowing a user to plugin a Version class that implements
Comparator
class MavenVersion implements ComparableMavenVersion
{
public int compareTo(MavenVersion o)
{
// your implementation
}
}
Then we can all do whatever we need.
On 27/09/2012 21:40, Hervé BOUTEMY wrote:
I understand that many people get caught
But what do you expect from [1.7,1.8]?
And [1.7,1.8-beta)?
The actual semantic is pure mathematical range, including or
excluding
an
extreme
since 1.8-alpha1.8-beta-1.8-rc1.8-SNAPSHOT1.8, it's pure
math
IMHO, anything that doesn't conform mathematical range will have
some
unexpected behaviour sometime
Yes, people need to learn that they usually want
[1.7,1.8-alpha-SNAPSHOT)
if
they want to be precise. Or approximations: [1.7,1.8-a),
[1.7,1.7.999]
Or we need to create another notation and define its semantics
precisely
Regards,
Hervé
Le jeudi 27 septembre 2012 20:46:08 Paul French a écrit :
+1
I agree with Jesse.
A version range like [1.7,1.8) should exclude any artifact that
starts
with 1.8
Then maven (or aether) would respect semantic versioning rules.
We use version ranges/semantic versioning and API analysis to
ensure
our
artifacts are versioned correctly. Sometimes we get caught out by
what
Jesse outlined below.
On 27/09/2012 15:51, Stephen Connolly wrote:
On 27 September 2012 14:41, Jesse Long j...@unknown.za.net
wrote:
Dear Maven Community,
I am writing to beg you to fix the problems with the version
ranges
in
Maven 3.0.5, specifically regarding the defining compatible
version
ranges.
I am using Maven 3.0.4. I have a simple project that depends on
