Question about release of Release

[Matthew Beermann <mb...@yahoo.com>]

(I asked this once before, but the thread got hijacked into other matters, so let's try this again...)

Will the next release of the Release plugin include the "generateReleasePoms" functionality, e.g. the creation of a POM with resolved versions? If you were to believe Better Builds with Maven (p224), this functionality exists already, except it doesn't actually seem to. There doesn't seem to be a JIRA issue that tracks this, at least that I was able to find. Nor is it entirely clear from the current source code in Subversion - lots of commented-out code with "TODOs".

This is key for us, and soon, as it helps to enable truly repeatable builds. Thanks for the help,

--Matthew Beermann

Re: Question about release of Release

[Nathan Beyer <nb...@gmail.com>]

On 11/8/06, Brett Porter <br...@apache.org> wrote:
> On 08/11/2006, at 5:10 PM, Nathan Beyer wrote:
>
> > On 11/7/06, Brett Porter <br...@apache.org> wrote:
> >> Yikes, I'm getting forgetful in my old age. I thought the section on
> >> that had been omitted from the final version of the book until it was
> >> implemented.
> >>
> >> Since we are no longer allowing changes to metadata in the repository
> >> (unless it is an extreme case), then repeatability shouldn't be a
> >> problem (notwithstanding bugs in the dependency mechanism which will
> >> effect it either way), unless you are using version ranges (which to
> >> date, haven't been popularly adopted because of the way they have
> >> been implemented). The main culprit is plugin versions, so populating
> >> those would be the most effective thing to do.
> >
> > The plugin versions are the exact issue. I'm a little surprised by the
> > suggestion to just add versions to the plugin references, as I don't
> > see this being done in the Maven projects themselves. Additionally,
> > this would erode a significant portion of the "convention over
> > configuration" philosophy, as this would require that all of the
> > plugins that are inferred would have to be explicitly added to every
> > POM. For example, the surefire plugin, which is rarely explicitly
> > added to the build section. Another example would be the compiler
> > plugin.
> >
>
> I agree - adding versioned plugin packs to maven 2.1 is one though to
> resolve the latter issue.
>
> By populating them, I did mean that the release plugin should assist
> with that as part of the release, which was what was originally
> requested.

Ahh, sorry. I read that incorrectly then, I thought you meant that
they should be manually populated.

-Nathan

>
> - Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: Question about release of Release

[Brett Porter <br...@apache.org>]

On 08/11/2006, at 5:10 PM, Nathan Beyer wrote:

> On 11/7/06, Brett Porter <br...@apache.org> wrote:
>> Yikes, I'm getting forgetful in my old age. I thought the section on
>> that had been omitted from the final version of the book until it was
>> implemented.
>>
>> Since we are no longer allowing changes to metadata in the repository
>> (unless it is an extreme case), then repeatability shouldn't be a
>> problem (notwithstanding bugs in the dependency mechanism which will
>> effect it either way), unless you are using version ranges (which to
>> date, haven't been popularly adopted because of the way they have
>> been implemented). The main culprit is plugin versions, so populating
>> those would be the most effective thing to do.
>
> The plugin versions are the exact issue. I'm a little surprised by the
> suggestion to just add versions to the plugin references, as I don't
> see this being done in the Maven projects themselves. Additionally,
> this would erode a significant portion of the "convention over
> configuration" philosophy, as this would require that all of the
> plugins that are inferred would have to be explicitly added to every
> POM. For example, the surefire plugin, which is rarely explicitly
> added to the build section. Another example would be the compiler
> plugin.
>

I agree - adding versioned plugin packs to maven 2.1 is one though to  
resolve the latter issue.

By populating them, I did mean that the release plugin should assist  
with that as part of the release, which was what was originally  
requested.

- Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: Question about release of Release

[Nathan Beyer <nb...@gmail.com>]

On 11/7/06, Brett Porter <br...@apache.org> wrote:
> Yikes, I'm getting forgetful in my old age. I thought the section on
> that had been omitted from the final version of the book until it was
> implemented.
>
> Since we are no longer allowing changes to metadata in the repository
> (unless it is an extreme case), then repeatability shouldn't be a
> problem (notwithstanding bugs in the dependency mechanism which will
> effect it either way), unless you are using version ranges (which to
> date, haven't been popularly adopted because of the way they have
> been implemented). The main culprit is plugin versions, so populating
> those would be the most effective thing to do.

The plugin versions are the exact issue. I'm a little surprised by the
suggestion to just add versions to the plugin references, as I don't
see this being done in the Maven projects themselves. Additionally,
this would erode a significant portion of the "convention over
configuration" philosophy, as this would require that all of the
plugins that are inferred would have to be explicitly added to every
POM. For example, the surefire plugin, which is rarely explicitly
added to the build section. Another example would be the compiler
plugin.

-Nathan

>
> It was my intention to review this overall with Maven 2.1 rather than
> slap this back onto the release plugin as it didn't have the full
> desired effect as is.
>
> - Brett
>
> On 08/11/2006, at 6:48 AM, Matthew Beermann wrote:
>
> > (I asked this once before, but the thread got hijacked into other
> > matters, so let's try this again...)
> >
> > Will the next release of the Release plugin include the
> > "generateReleasePoms" functionality, e.g. the creation of a POM
> > with resolved versions? If you were to believe Better Builds with
> > Maven (p224), this functionality exists already, except it doesn't
> > actually seem to. There doesn't seem to be a JIRA issue that tracks
> > this, at least that I was able to find. Nor is it entirely clear
> > from the current source code in Subversion - lots of commented-out
> > code with "TODOs".
> >
> > This is key for us, and soon, as it helps to enable truly
> > repeatable builds. Thanks for the help,
> >
> > --Matthew Beermann
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: Question about release of Release

[Mark Hobson <ma...@gmail.com>]

On 15/11/06, Gabriele Contini <gc...@hotpop.com> wrote:
> We are currently facing this problem :
> -we have about 50 modules with various level of dependencies
> -developers need to work using module SNAPSHOTs
> - the release plugin requires RELEASE dependencies
> - we really cannot modify every pom by hand at every change
>
> So we decided to use version ranges, and that works like a charm (almost).
> In order to have truly repeatable builds with version ranges we really
> need the "generateReleasePoms" working... Do you have any other
> suggestion? Are we mistaking the way maven should be used?

We have similar problems here and have considered using version
ranges, but was unaware of the generateReleasePoms option.  See my
posting on similar thread here:

http://www.mail-archive.com/users@maven.apache.org/msg54759.html

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: Question about release of Release

[Gabriele Contini <gc...@hotpop.com>]

We are currently facing this problem :
-we have about 50 modules with various level of dependencies
-developers need to work using module SNAPSHOTs
- the release plugin requires RELEASE dependencies
- we really cannot modify every pom by hand at every change

So we decided to use version ranges, and that works like a charm (almost).
In order to have truly repeatable builds with version ranges we really 
need the "generateReleasePoms" working... Do you have any other 
suggestion? Are we mistaking the way maven should be used?
Thanks in advance,
Gabriele


Brett Porter wrote:
> Yikes, I'm getting forgetful in my old age. I thought the section on 
> that had been omitted from the final version of the book until it was 
> implemented.
>
> Since we are no longer allowing changes to metadata in the repository 
> (unless it is an extreme case), then repeatability shouldn't be a 
> problem (notwithstanding bugs in the dependency mechanism which will 
> effect it either way), unless you are using version ranges (which to 
> date, haven't been popularly adopted because of the way they have been 
> implemented). The main culprit is plugin versions, so populating those 
> would be the most effective thing to do.
>
> It was my intention to review this overall with Maven 2.1 rather than 
> slap this back onto the release plugin as it didn't have the full 
> desired effect as is.
>
> - Brett
>
> On 08/11/2006, at 6:48 AM, Matthew Beermann wrote:
>
>> (I asked this once before, but the thread got hijacked into other 
>> matters, so let's try this again...)
>>
>> Will the next release of the Release plugin include the 
>> "generateReleasePoms" functionality, e.g. the creation of a POM with 
>> resolved versions? If you were to believe Better Builds with Maven 
>> (p224), this functionality exists already, except it doesn't actually 
>> seem to. There doesn't seem to be a JIRA issue that tracks this, at 
>> least that I was able to find. Nor is it entirely clear from the 
>> current source code in Subversion - lots of commented-out code with 
>> "TODOs".
>>
>> This is key for us, and soon, as it helps to enable truly repeatable 
>> builds. Thanks for the help,
>>
>> --Matthew Beermann
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: Question about release of Release

[Brett Porter <br...@apache.org>]

Yikes, I'm getting forgetful in my old age. I thought the section on  
that had been omitted from the final version of the book until it was  
implemented.

Since we are no longer allowing changes to metadata in the repository  
(unless it is an extreme case), then repeatability shouldn't be a  
problem (notwithstanding bugs in the dependency mechanism which will  
effect it either way), unless you are using version ranges (which to  
date, haven't been popularly adopted because of the way they have  
been implemented). The main culprit is plugin versions, so populating  
those would be the most effective thing to do.

It was my intention to review this overall with Maven 2.1 rather than  
slap this back onto the release plugin as it didn't have the full  
desired effect as is.

- Brett

On 08/11/2006, at 6:48 AM, Matthew Beermann wrote:

> (I asked this once before, but the thread got hijacked into other  
> matters, so let's try this again...)
>
> Will the next release of the Release plugin include the  
> "generateReleasePoms" functionality, e.g. the creation of a POM  
> with resolved versions? If you were to believe Better Builds with  
> Maven (p224), this functionality exists already, except it doesn't  
> actually seem to. There doesn't seem to be a JIRA issue that tracks  
> this, at least that I was able to find. Nor is it entirely clear  
> from the current source code in Subversion - lots of commented-out  
> code with "TODOs".
>
> This is key for us, and soon, as it helps to enable truly  
> repeatable builds. Thanks for the help,
>
> --Matthew Beermann
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org