File name encoding at mvn deploy?

2009-07-20 Thread Ringo De Smet
Hello, I have a small problem with Maven (2.2.0) deploying to Nexus (1.3.5). I am evaluating Maven + freehep-nar-plugin (1) to build native projects. The plugin adds additional .nar files to the deployment of my Maven module. Some of these files contain platform specific information in the file na

maven-release-plugin: branch goal does not take same properties as prepare goal

2009-03-26 Thread Ringo De Smet
Hello, I am trying to automate the branching for a few hundred Maven projects. The automation of creating a release works great using the -DreleaseVersion and -DdevelopmentVersion properties using the prepare goal. The documentation of the branch goals states this: "The branch goal can use the sam

Re: Aren't ranges allowed when releasing?

2009-03-24 Thread Ringo De Smet
Chris, > 2009/3/19 > >> I'm trying to release a project, that has these dependencies in it. It >> works fine for install/package etc, but only when releasing does it >> complain. >> >> If it can choose the correct one to compile and package against, why can we >> not trust it to choose it when re

Re: Checking the java class version in maven artifacts

2009-03-23 Thread Ringo De Smet
a specific + * Java version. + * + * @author Ringo De Smet + * @phase verify + * @goal classVersions + */ +public class ClassVersionMojo extends AbstractMojo { + + private final static Map JAVA_VERSIONS_MAP; + + static { + JAVA_VERSIONS_MAP = new HashMap();

Re: Plugin to validate the class file version of built artifacts?

2009-03-18 Thread Ringo De Smet
2009/3/17 Stephen Connolly : > google this "animal sniffer Kohsuke" > > it should give you what you're after Thanks Stephen, this was what I was looking for! For the email archives: http://animal-sniffer.dev.java.net Ringo - To

Re: Version ranges

2009-03-17 Thread Ringo De Smet
2009/3/11 Johannes Schneider : > There is a dependency to Jide defined: > > [2.2.0, 3.0.0) > > Could anyone give me a hint how to solve this? Drop the build number from your starting version, only leaving the major and minor part: [2.2, 3.0.0) Leaving the build number out of your version specifi

Re: Plugin to validate the class file version of built artifacts?

2009-03-17 Thread Ringo De Smet
Dirk, 2009/3/17 Dirk Olmes : > > Can't you just configure a JDK1.4 in hudson to use for compiling/running > Maven on the jobs that build your project? The tight Maven2 build support in Hudson, including the Maven module dependency support, requires that your Maven runs in Java 1.5 unfortunately.

Re: Plugin to validate the class file version of built artifacts?

2009-03-17 Thread Ringo De Smet
Gabriele, 2009/3/17 Gabriele Columbro : > Maybe you're referring to the maven-enforcer-plugin? [1] > > I've never used personally so not sure if it can accomplish your goal, but > hopefully can help ;) > Nope, that's not the one. This one check that you are running under a specific JVM version. I

Re: How to use maven-release-plugin to build/release from a branch?

2009-03-17 Thread Ringo De Smet
Eric, 2009/3/16 Eric B. : > Hi, > > How can I use the release:perform goal in the maven-release-plugin to build > my module located in a CVS branch? > > I have tried mvn release:perform -DtagBase=B_2_0_0 hoping / expect that it > would pass the tagBase command along to CVS to checkout the sources

Re: Maven-scm-plugin define -Dmaven.scm.provider.cvs.implementation in pom?

2009-03-17 Thread Ringo De Smet
2009/3/16 Eric B. : > > I've been trying to figure out if there is a way to specify the > maven.scm.provider.cvs.implementation in the pom or in a profile, but > haven't been able to find anything.  I know I can > specify -Dmaven.scm.provider.cvs.implementation=cvs_native on the command > line, but

Plugin to validate the class file version of built artifacts?

2009-03-17 Thread Ringo De Smet
Hello, Our current build system is based on JDK 1.4.2 and Maven 2.0.9. We are in the process of migrating from Continuum to Hudson. Hudson requires Java 1.5 for its Maven2 integration. I already updated the configuration of some of the plugins to make sure that 1.4 compatible bytecode is generated

Re: maven-compiler-plugin - where does it take compiler from?

2009-03-13 Thread Ringo De Smet
2009/3/13 Nick Stolwijk : > It will use the build-in compiler in your JDK you are using to run > Maven. So just make sure every developer uses the right JDK version. And if you want to enforce it, use the maven-enforcer-plugin to make sure builds only take place in the correct JDK version: http:/

Re: scm:update pom.xml to latest version on branch when checked out by tag

2009-02-18 Thread Ringo De Smet
2009/2/18 Mark Struberg : > what do you mean with: >> tag one of your projects with "code_to_include_in_release" > ? > you surely mean the tag which will automatically be created via > realease:prepare, don't you? No. Read my first mail: developers tag the code that they want to go into a release

Re: scm:update pom.xml to latest version on branch when checked out by tag

2009-02-18 Thread Ringo De Smet
Mark, 2009/2/18 Mark Struberg : > maybe I did not understand what you really like to do, but did you look at > release:rollback? This will revert the pom back to the original status. > > One for sure: the scm providers won't help you much when it comes to > manipulating the pom.xml. They are str

scm:update pom.xml to latest version on branch when checked out by tag

2009-02-18 Thread Ringo De Smet
Hello, This is actually a repost of this message: http://markmail.org/message/2xzsgvxmln5krgdl However, no answers came and I didn't find a solution yet. I check out a project based on a floating tag in CVS. The tag indicates the code that can go in a release. Before the release plugin can update