On 09/01/2012 15:48, Igor Fedorenko wrote:
    
      On 12-01-09 7:18 AM, Mickael Istria wrote:
       
      On 09/01/2012 12:59, Igor Fedorenko wrote:
         
        Parent coordinates have to be constants,
          otherwise Maven will not be
           
          able to load build extensions that provide Tycho-specific
          behaviour. The
           
          same probably applies to artifactId and packaging, but I am
          not 100% sure.
           
         
        Ok, that's what I thought too.
         
         
        I do not believe there are any
          fundamental restrictions on other parts
           
          of pom.xml, but implementation may or may not be possible
          without
           
          changes to Maven core.
           
         
        It would probably make more sense to have ${manifest.*} in Maven
        core
         
        rather than just in Tycho. It is not related to p2, and any
        Maven
         
        project could use it.
         
         
       
       
      Not sure I follow. Most non-Tycho Maven projects do not have
       
      hand-written manifest in their sources, what values would be used
      for
       
      ${manifest.*} in such projects?
       
     
     
    I agree this would only make sense when a MANIFEST.MF does exist. If
    you say this is very specific to Tycho projects, I trust you. My
    point was that the MANIFEST.MF file is also "classic" Java stuff, so
    maybe it would be useful in a wider context. 
     
    
      
        The real question, though, is it worth
          the trouble?
           
         
        I think that although it is not that difficult to synchronize
        pom and
         
        manifest, it is one more (easy to forget and annoying) step to
        do when
         
        maintaining a project. And having the opportunity to reference
        MANIFEST
         
        in artifactId and version -and then to have automatic
        synchronization-
         
        would be a great step forward conceptually. It would make Tycho
        even
         
        more OSGi-friendly,
         
         
        So it would be very nice to have it,
         
         
        But that's not an immediate requirement, just more food for
        thoughts.
         
       
       
      Well, in this case why not take things even further and get rid of
      the
       
      pom altogether? 
     
    Very good suggestion ;) 
    I think that would be a very nice approach: have maven generate
    _dynamically_ an in-memory pom description from a MANIFEST while
    building in case a pom.xml does not already exists.  
     
    Most
      Tycho projects have very basic pom.xml files, which
      can be easily derived from other metadata.
       
     
     
    I am aware that. But I am more thinking about making it even easier. 
    
  
 |