*Robert:*
I actually relaxed "no module nesting" requirement. just not tested
well yet.
Thank you,
Andrei
Original Message
Subject: Re: Multi-project releases
From: Robert Scholte
To: Maven Developers List
Date: Wed 27 Mar 2013 03:59:42 PM CDT
e name of "layout project".
>>
>> I also go 2 steps further:
>> 1) I require that there are no declarations in non-root
>> projects, so all modules and parents are independent.
>> 2) I do recursive release of the whole layout automatically, from any
>>
the middle tree, releasing what needs be released.
Original Message
Subject: Re: Multi-project releases
From: Stephen Connolly
To: Andrei Pozolotin
Cc: Maven Developers List , Robert Scholte
Date: Sun 24 Mar 2013 03:59:40 PM CDT
There is a trick called the "local aggregator p
sharing is a key. I suggest you change your assumption to have
aggregation pom be part of the source repo
Original Message
Subject: Re: Multi-project releases
From: Stephen Connolly
To: Maven Developers List
Date: Sun 24 Mar 2013 05:55:56 PM CDT
> I usually don't check
is there a way to designate local-aggregator poms as such? say, have
version = 0.0.0, since they are never released.
Original Message
Subject: Re: Multi-project releases
From: Robert Scholte
To: Maven Developers List
Date: Sun 24 Mar 2013 04:44:20 PM CDT
> Let me answer my
Jeff got it, thank you. Andrei
Original Message
Subject: Re: Multi-project releases
From: Jeff Jensen
To: Maven Developers List
Date: Sun 24 Mar 2013 04:00:28 PM CDT
> I am not aware of a Maven feature to fully ignore them other than -N with
> the tag caveat. When I&#
independent.
2) I do recursive release of the whole layout automatically, from any
point in the middle tree, releasing what needs be released.
Original Message ----
Subject: Re: Multi-project releases
From: Stephen Connolly
To: Andrei Pozolotin
Cc: Maven Developers List , Robert Scholte
Date
mean by "release root"?
> * can release root contain other release roots as modules?
> * can I release the release root w/o releasing the release root modules?
> (need a better term :-))
> * can your envisioned plugin automatically recursively release all other
> dependencie
other
dependencies moving upward in the reactor dependency tree?
---- Original Message
Subject: Re: Multi-project releases
From: Stephen Connolly
'stephen.alan.conno...@gmail.com');>
To: Andrei Pozolotin
Cc: Maven Developers List 'cvml', 'dev@maven.apa
her
dependencies moving upward in the reactor dependency tree?
---- Original Message
Subject: Re: Multi-project releases
From: Stephen Connolly
'stephen.alan.conno...@gmail.com');>
To: Andrei Pozolotin
Cc: Maven Developers List 'cvml', 'dev@maven.apache.org&
uot;where these required-to-be-released-artifacts live? "
> by looking into tag, and using still one more convention (to be
> decided)
> where to look locally before attempting independent remote clone.
>
> ---- Original Message
> Subject: Re: Multi-project releases
>
t;.
>
> so what is the way to release a parent w/o its modules?
>
> Original Message ----
> Subject: Re: Multi-project releases
> From: Stephen Connolly
> To: Maven Developers List
> Date: Sun 24 Mar 2013 02:30:10 PM CDT
> > That's still goin
e the release root w/o releasing the release root modules?
> (need a better term :-))
> * can your envisioned plugin automatically recursively release all other
> dependencies moving upward in the reactor dependency tree?
>
> Original Message
> Subject: Re: M
t; > unrelated question, may be you can clarify: in the current
> > > maven-release-plugin
> > > what is the way to release parent w/o releasing its modules?
> > >
> > > Thank you,
> > >
> > > Andrei
> > &g
re: "where these required-to-be-released-artifacts live? "
by looking into tag, and using still one more convention (to be
decided)
where to look locally before attempting independent remote clone.
Original Message
Subject: Re: Multi-project releases
From: Fred Cooke
e all other
> dependencies moving upward in the reactor dependency tree?
>
> Original Message
> Subject: Re: Multi-project releases
> From: Stephen Connolly
> To: Andrei Pozolotin
> Cc: Maven Developers List , Robert Scholte
>
> Date: Sun 24 Mar 2013 02:32:3
I do not mind - "children being part of the tag ".
so what is the way to release a parent w/o its modules?
Original Message
Subject: Re: Multi-project releases
From: Stephen Connolly
To: Maven Developers List
Date: Sun 24 Mar 2013 02:30:10 PM CDT
> That
ur envisioned plugin automatically recursively release all other
dependencies moving upward in the reactor dependency tree?
Original Message ----
Subject: Re: Multi-project releases
From: Stephen Connolly
To: Andrei Pozolotin
Cc: Maven Developers List , Robert Scholte
Date: Sun 24 Mar
wiki page somewhere to flesh out all
> > assumptions that currently go into release
> > as well as to list the use cases people really need. here is one of my
> use
> > cases:
> >
> >
> https://github.com/barchart/barchart-jenkins-tester-ecosystem/blob/master/readme.md
> &
. here is one of my use
> cases:
>
> https://github.com/barchart/barchart-jenkins-tester-ecosystem/blob/master/readme.md
>
> Andrei
>
> Original Message
> Subject: Re: Multi-project releases
> From: Robert Scholte 'rfscho...@apache.org');>
> T
gt; is a
> > >> wrong approach.
> > >> please consider instead "start-from-any-module / from-bottom-up /
> > >> incremental" approach, as implemented here:
> > >> https://github.com/barchart/barchart-jenkins-cascade-plugin/wiki
> > >&
what is the way to release parent w/o releasing its modules?
>
> Thank you,
>
> Andrei
>
> Original Message ----
> Subject: Re: Multi-project releases
> From: Robert Scholte
> To: Maven Developers List , Andrei Pozolotin
>
> Cc: "Stephen Co
*Robert*
unrelated question, may be you can clarify: in the current
maven-release-plugin
what is the way to release parent w/o releasing its modules?
Thank you,
Andrei
Original Message
Subject: Re: Multi-project releases
From: Robert Scholte
To
ll be used by a release-like plugin. well,
never mind, I guess it is too early for questions.
Thank you,
Andrei
Original Message
Subject: Re: Multi-project releases
From: Robert Scholte
To: Maven Developers List , Andrei Pozolotin
Cc: "Stephen Connolly"
ases people really need. here is one of my
use cases:
https://github.com/barchart/barchart-jenkins-tester-ecosystem/blob/master/readme.md
Andrei
Original Message ----
Subject: Re: Multi-project releases
From: Robert Scholte
To: Maven Developers List
Date: Sun 24 Mar 2013 09:42:27
--- Original Message ----
Subject: Re: Multi-project releases
From: Robert Scholte
To: Maven Developers List
Date: Sun 24 Mar 2013 09:42:27 AM CDT
> Hi Stephen,
>
> I've just checked your code.
> Most interesting is our difference of the definition "releaseRoot" (o
Well I see a release root as being where there is a non-inherited SCM
If there are changes since the last release (or no last release) then it
*should*/*could* be released which is what that plugin reports.
More interesting to me would be if a child project defines SCM that is
identical to the
Hi Stephen,
I've just checked your code.
Most interesting is our difference of the definition "releaseRoot" (or in
my case rootProject, I think we mean the same thing with it).
If I'm correct you base it on the existence of the -section and if it
has ever been released (assuming a specific sc
Hi,
I've made a start, see http://svn.apache.org/r1460347
There are IT's for resolving the site URL, for SCM URLs it should be more
of the same.
It's open for discussion.
Robert
Op Fri, 15 Mar 2013 05:14:00 +0100 schreef Rahul Thakur
:
And something like a CI server can make use of thi
And something like a CI server can make use of this capability as well.
On 3/15/2013 2:20 AM, Robert Scholte wrote:
At least the maven-help-plugin and probably the maven-site-plugin too.
There's a small difference between the resolved pom for Maven(core)
and the way paths are transformed for
This is an interesting discussion as well as a very relevant direction of
thoughts.
I feel that the maven distribution strategies (mainly within site/release
plugins) are full of
[fairly undocumented] assumptions - the net result of which is a confusing
experience
for the users.
It would seem that
At least the maven-help-plugin and probably the maven-site-plugin too.
There's a small difference between the resolved pom for Maven(core) and
the way paths are transformed for the maven-release-plugin and
maven-site-plugin.
here are some examples:
https://jira.codehaus.org/browse/MSITE-669
On Thursday, 14 March 2013, Robert Scholte wrote:
> Let's create a new shared component[1] for it: there are more plugins
> depending on this intelligence.
What other plugins could be concerned with knowing which projects are roots
for the release plugin?
Or maybe you gave something else in min
Let's create a new shared component[1] for it: there are more plugins
depending on this intelligence.
Looks to me there's no component for this kind of stuff yet.
Robert
[1] http://maven.apache.org/shared/index.html
Op Thu, 14 Mar 2013 10:32:26 +0100 schreef Stephen Connolly
:
No it mak
No it makes more sense in the release plugin
On 14 March 2013 09:16, Rahul Thakur wrote:
>
> And perhaps this capability can reside in Maven core? Just a thought
>
>
>
>
> On 3/12/2013 2:56 AM, Robert Scholte wrote:
>
>> Hi,
>>
>> There are several MSITE/DOXIA and MRELEASE issues related to
And perhaps this capability can reside in Maven core? Just a thought
On 3/12/2013 2:56 AM, Robert Scholte wrote:
Hi,
There are several MSITE/DOXIA and MRELEASE issues related to this
subject.
For the SCM-section and the site-section of the distributionManagement
we need a more intell
Cool, thanks :)
-Deng
On Wed, Mar 13, 2013 at 3:38 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> I thought I had included the link... But it does not seem there now...
> Strange
>
> https://github.com/stephenc/mpr-maven-plugin
>
> On Wednesday, 13 March 2013, Deng Ching-Mallet
I thought I had included the link... But it does not seem there now...
Strange
https://github.com/stephenc/mpr-maven-plugin
On Wednesday, 13 March 2013, Deng Ching-Mallete wrote:
> Hi Stephen,
>
> Where can I get/checkout the plugin? We have a project with the same
> structure so I'd like to try
Hi Stephen,
Where can I get/checkout the plugin? We have a project with the same
structure so I'd like to try it out.
Thanks,
Deng
On Mon, Mar 11, 2013 at 7:50 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hey one and all,
>
> So we all know how multiple projects with multipl
Hi,
There are several MSITE/DOXIA and MRELEASE issues related to this subject.
For the SCM-section and the site-section of the distributionManagement we
need a more intelligent way to resolve this.
Right now this logic is hidden inside the maven-release-plugin and
maven-site-plugin, causing
children with parent.
(i.e. I want to release parent of multi-module project w/o children)
Thank you,
Andrei
Original Message
Subject: Re: Multi-project releases
From: Stephen Connolly
To: Andrei Pozolotin
Cc: Maven Developers List
Date: Mon 11 Mar 2013 10:32:45
March 2013 14:18, Andrei Pozolotin wrote:
> * Stephen**
> *
> I made this solution for the problem:
> https://github.com/barchart/barchart-jenkins-cascade-plugin/wiki
>
> Please let me know what you think?
>
> Thank you,
>
> Andrei
>
> ---- Original
*Stephen**
*
I made this solution for the problem:
https://github.com/barchart/barchart-jenkins-cascade-plugin/wiki
Please let me know what you think?
Thank you,
Andrei
Original Message
Subject: Multi-project releases
From: Stephen Connolly
To
[ http://jira.codehaus.org/browse/MPSCM-39?page=history ]
Brett Porter updated MPSCM-39:
--
Fix Version: (was: 1.5)
1.6
> Support for branching and non-interactive multi-project relea
: MPSCM-39
Summary: Support for branching and non-interactive multi-project releases
Type: New Feature
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-scm-plugin
Fix Fors:
1.5
Versions
is an overview of the issue:
-
Key: MPSCM-39
Summary: Support for branching and non-interactive multi-project releases
Type: New Feature
Status: Open
Priority: Major
Original Estimate: Unknown
Time
:
-
Key: MPSCM-39
Summary: Support for branching and non-interactive multi-project releases
Type: New Feature
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
: MPSCM-39
Summary: Support for branching and non-interactive multi-project releases
Type: New Feature
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-scm-plugin
Versions:
1.4.2
Assignee
48 matches
Mail list logo
