Re: Dependencies question

If a library A that you call, calls a method mailme in library B , you can not remove that library unless you are supplying a later version of the library B with the mailme method through another dependency. If mailme was deprecated and removed in the later version of B, you will not be able

Re: Embedded java 6 librairies

We can't read your email. Please stop using nabble. All the XML is missi g. On Mon, Jan 7, 2013 at 2:16 AM, adrien ruffie adriennolar...@hotmail.frwrote: Hello all, I my application I have following jar declared as a Maven dependencies: serializer.jar, xercesImpl-2.8.1.jar,

building from latest trunk

Hi, I did openVMS bash$ svn co trunk bash$ mvn clean install bash$ all the build steps indicates SUCCESS; lets do a cd and inspect bash$ cd /dka3/.m2/repository/org/apache/maven/apache-maven/3.1-SNAPSHOT bash$ ls -l total 10205 -rwxr-x--- 1 STADELMA 129 5206734 Jan 7 12:12

Re: building from latest trunk

Not an answer for you but an FYI: Maven trunk has moved to git On 7 January 2013 13:47, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Hi, I did openVMS bash$ svn co trunk bash$ mvn clean install bash$ all the build steps indicates SUCCESS; lets do a cd and inspect

AW: building from latest trunk

Thanks Steven, I assumed that! BUT are you saying that $ svn up does no longer work ... AND For me there is to say I do not have a git for OpenVMS yet, hence this circumstances will complicate my src update cycles, unless someone knows about a OpenVMS port of GIT! Are you further saying

Re: building from latest trunk

2013/1/7 Stadelmann Josef josef.stadelm...@axa-winterthur.ch: Thanks Steven, I assumed that! BUT are you saying that $ svn up does no longer work ... AND For me there is to say I do not have a git for OpenVMS yet, hence this circumstances will complicate my src update cycles, unless

Re: building from latest trunk

Those docs are in the process of being rewitten... they are sadly not what they should be. AFAIK you will need GIT to get the latest core distribution... If you dont need latest, you can get the release tarballs... And there is always the ability to get a .zip of the core source though some

Re: Maven versioning

Thanks Ron. That makes more sense to not bump the versions in the event the libraries do not change. For some reason a lot of the examples out there show the dependency versions to be ${project.version}, which would save a person from updating the poms but would cause me to unnecessarilly have

Re: building from latest trunk

On Mon, Jan 7, 2013 at 3:32 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Those docs are in the process of being rewitten... they are sadly not what they should be. AFAIK you will need GIT to get the latest core distribution... If you dont need latest, you can get the release

AW: building from latest trunk

Does that mean that I can still use jsvn to update my maven trunk sources but this time just from a different (git-hub)repository found under a different url? if yes: what is the correct svn checkout command to use? Thanks Josef -Ursprüngliche Nachricht- Von: Thomas Broyer

Re: building from latest trunk

On Mon, Jan 7, 2013 at 4:20 PM, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Does that mean that I can still use jsvn to update my maven trunk sources but this time just from a different (git-hub)repository found under a different url? AIUI, yes. if yes: what is the correct

snapshot versions and classpath stored in manifest

Hello all, I am using Maven 3 with Nexus 2. I am building a cli tool (let's call it cli) , which has dependencies on some other libraries (let's call them dependencyA and dependencyB) To make my cli tool work in every environment, I rely on the manifest classpath, generated with : plugin

Re: JNI jars dependencies

Hi all, http://dev.loci.wisc.edu/trac/software/browser/branches/maven/projects/native-library-util/src/main/java/com/wapmx/nativeutils/jniloader/NativeLoader.java?rev=7574 Some notes about this code: 1) The above URL is to an SVN repository that has since been migrated to Git. The current URL

Re: JNI jars dependencies

Hi Stuart, I didn't use NAR as I was worried it was unsupported,fragmented and overly optimistic on what it was trying to achieve. FYI, there is now an attempt at unification of the maven-nar-plugin at: https://github.com/maven-nar/maven-nar-plugin As well as a maven-nar-plugin mailing

Re: [ANN] Maven Release Plugin 2.4 Released

[-announce] There are known issues between the 2.4 plugin and the SCM integration for git. See http://mail-archives.apache.org/mod_mbox/maven-users/201301.mbox/%3CA94BB529DDA042A281B039C400250037%40turn.com%3E and following messages for open bugs tracking at least one issue which appears

Re: [ANN] Maven Release Plugin 2.4 Released

Hrm - reading your post makes it sound like the two options I mentioned I'm using ( pushChangesfalse/pushChanges and localCheckouttrue/localCheckout ) are possibly now applied by default - which was proposed ages ago as the preferred behaviour for distributed version control systems ( as their

Re: Release preparation not removing SNAPSHOT suffix

I've checked your output and these lines are parsed as expected. Somehow the output was different during the release, because that didn't recognize any changed files. Mark Struberg told me that the GIT output is written to a file somewhere under target. Otherwise I could use some

assembly plugin logging anomaly

Using the assembly plugin I have a file set defined with fileMode644/fileMode directoryMode755/directoryMode This works correctly - the archive generated has the desired permissions. But the logging says [DEBUG] FileSet[outputDir/] dir perms 4 file perms 10 What notation system is this

Re: Fitnesse support?

During 2012 I wrote a plugin, as none of the others were doing quite what I wanted. https://code.google.com/p/fitnesse-launcher-maven-plugin/ -- View this message in context: http://maven.40175.n5.nabble.com/Fitnesse-support-tp3393137p5742540.html Sent from the Maven - Users mailing list

Re: Fitnesse support?

Tried this one? https://github.com/lvonk/fitnesse-maven-classpath 2013/1/7 javahelp stew...@javahelp.co.uk During 2012 I wrote a plugin, as none of the others were doing quite what I wanted. https://code.google.com/p/fitnesse-launcher-maven-plugin/ -- View this message in context:

Re: Should I add tools.jar to my internal repo?

Hi everyone, I consider any project that has a dependency to tools.jar as broken. The question follows: What is the Maven best practice for a project that needs a Java compiler? (Formerly com.sun.tools.javac.Main, com.sun.tools.apt.Main, etc.; now javax.tools.JavaCompiler as of Java 6.) The

Set maven.compiler.target on command-line

The maven-compiler-plugin allows one to set the maven.compiler.target property in the POM, the value of which is in turn passed as the -target argument to the Java compiler. I would like to be able to set this maven.compiler.target on the command-line instead, as follows: mvn clean compile

Re: Set maven.compiler.target on command-line

You can define a property in your Pom file and then set the configuration with that property and then use the cli to override that property... But the bigger question is *why* do you think you want to do this? Most likely you don't and instead animal-sniffer is what you want... Or perhaps there

maven property resolution

Hi, I'm writing a plugin and need to be able to dynamically resolve properties (e.g. project.version, java.version, etc). Does anyone know which component does this? The neither the maven project properties not the session execution properties have them. Thanks!

Re: maven property resolution

Found it! org.codehaus.plexus.util.introspection.ReflectionValueExtractor :) On Jan 7, 2013, at 8:05 PM, Marcos Mendez wrote: Hi, I'm writing a plugin and need to be able to dynamically resolve properties (e.g. project.version, java.version, etc). Does anyone know which component does

inconsistencies found with maven-site-plugin

Manfred from the trunk\pom.xml the maven-android-plugin pom.xml was abending on executions when maven-surefire plugin was being referenced from within maven-site-plugin here is the applicable portion of pom.xmlplugin groupIdorg.apache.maven.plugins/groupId