camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Matèrne (jhm) <apa...@materne.de>
Subject AW: [IDEA] - Having a parent maven pom.xml for only the dependency versions
Date Sat, 17 Aug 2013 20:23:42 GMT
I just played with that maven plugin.
The problem is that it loads the properties after the validation phase.

That wont work:

<!-- http://mojo.codehaus.org/properties-maven-plugin/usage.html -->
<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>just-test</groupId>
  <artifactId>version-test</artifactId>
  <version>1.0</version>
  
  <build>
    <plugins>
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>properties-maven-plugin</artifactId>
        <version>1.0-alpha-2</version>
        <executions>
          <execution>
            <phase>initialize</phase>
            <goals>
              <goal>read-project-properties</goal>
            </goals>
            <configuration>
              <files>
                <file>versions.properties</file>
              </files>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
  
  <dependencies>
    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>${junit}</version>
    </dependency>
  </dependencies>
</project>


I also tried putting a
  <properties>
    <junit>1</junit>
  </properties>
as placeholder for the validation doesnt work.
The property is not changed to the stored junit=4.9 in my file.


Current ideas:
- building our own mvn plugin (enhancing that plugin) for loading the props
and overwrite existing properties
- generate a valid pom from the version-list


Jan


> -----Urspr√ľngliche Nachricht-----
> Von: Babak Vahdat [mailto:babak.vahdat@swissonline.ch]
> Gesendet: Samstag, 17. August 2013 21:48
> An: dev@camel.apache.org
> Betreff: Re: [IDEA] - Having a parent maven pom.xml for only the
> dependency versions
> 
> Hi
> 
> what I'm aware of for this purpose is the following plugin:
> 
> http://mojo.codehaus.org/properties-maven-plugin/usage.html
> 
> However it's not maintained anymore since 2009!
> 
> The other option would be to use the Kuali's plugin but I'm not sure
> about it's licence (it's already available in central repo):
> 
> http://site.kuali.org/maven/plugins/properties-maven-plugin/1.1.9/read-
> project-properties-mojo.html
> 
> No matter which one we would want to make use of, the tough part of
> this would be to convert the lines like:
> 
> <ahc-version>1.7.19</ahc-version>
> 
> into:
> 
> ahc-version=1.7.19
> 
> But it should be possible to automate this conversion with couple of
> lines of code, or maybe even a new Camel date format for this purpose
> :-)
> 
> Babak
> 
> 
> Claus Ibsen-2 wrote
> > Hi
> >
> > Today we have the parent/pom.xml file which has both all the versions
> > of the 3rd party JARs we have as dependencies. And also a list of all
> > the camel components and some other stuff.
> >
> > I wonder if we could have all the dependency versions in a single
> > file, without all the other stuff.
> >
> > This would make it easier for ppl to see what are the version changes
> > between any two Camel versions, but just diff the 2 files?
> >
> > And also we could just have such a link in the release notes so we
> > dont have to manually keep all the versions upgrades in the release
> > notes up to date as well.
> >
> > --
> > Claus Ibsen
> > -----------------
> > Red Hat, Inc.
> > Email:
> 
> > cibsen@
> 
> > Twitter: davsclaus
> > Blog: http://davsclaus.com
> > Author of Camel in Action: http://www.manning.com/ibsen
> 
> 
> 
> 
> 
> --
> View this message in context: http://camel.465427.n5.nabble.com/IDEA-
> Having-a-parent-maven-pom-xml-for-only-the-dependency-versions-
> tp5737322p5737460.html
> Sent from the Camel Development mailing list archive at Nabble.com.


Mime
View raw message