You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Al Maw <wi...@almaw.com> on 2007/03/09 15:14:52 UTC
VOTE: Move modules around to make releasing easier in 1.x branch
(and rename branch).
As detailed in the thread "almaw's new build-test branch" I've been
thinking about how to make the release process work more smoothly.
I've restructured how 1.3 is parented, etc. in the branch
"al-test-wicket-1.3.x". You can see how it looks here:
http://svn.apache.org/viewvc/incubator/wicket/branches/al-test-wicket-1.3.x/
Advantages:
- It massively simplifies the pom.xml files and reduces redundancy and
duplication, and removes the potential for the configuration of the
various modules getting out of sync.
- It's really obvious which projects need JDK 5 and which don't.
- We will hopefully be able to use the Maven 2 release plug-in for
the jdk-1.4 and jdk-1.5 bits and make everything more automated.
- We don't need -P profile switches to build things any more.
- Getting the whole shooting match into Eclipse is now:
- One command to check it out.
- One command to build the Eclipse .project, etc. files.
- Three clicks in Eclipse to import all the projects, which will
then all depend on each other correctly.
- Removes the wicket-parent project, which is a bit mystical and lots
of people don't discover by themselves.
Disadvantages:
- Everyone will need to update their workspaces.
So, please vote:
================
[ ] Yes, change the 1.x branch so it looks like that.
[ ] No, don't restructure it! That's a rubbish idea!
We could also take this opportunity to rename the 1.x branch to 1.3.x.
If you voted yes above, please also vote:
=========================================
[ ] Yes, rename the branch to "wicket-1.3.x" at the same time so I
only need to set my IDE workspace up again once.
[ ] No, don't rename the branch, we'll postpone that until we
release a beta, or a 1.3.0 final, or something.
Given it's a bit of a faff for everyone, if this does go ahead I will
post a time when I will move stuff at least a couple of days in advance
so people can get their outstanding commits in, which should make it
easy for everyone.
If you were to have outstanding commits when things are moved, svn will
keep the changes in orphaned files so you can move them across manually
to the new layout. It's just a little less convenient.
Al
Re: VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Jean-Baptiste Quenot <jb...@apache.org>.
> So, please vote:
> ================
>
> [X] Yes, change the 1.x branch so it looks like that.
>
> [ ] No, don't restructure it! That's a rubbish idea!
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
Re: VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Eelco Hillenius <ee...@gmail.com>.
Sweet! That's what I want!
Eelco
On 3/9/07, Igor Vaynberg <ig...@gmail.com> wrote:
> mvn eclipse:eclipse in al-test-wicket-1.3.x does this :) one command builds
> eclipse projects for everything that depend on each other rather then jars
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Wicket Parent ......................................... SUCCESS [
> 4.854s]
> [INFO] Wicket JDK 1.4 modules ................................ SUCCESS [
> 0.255s]
> [INFO] Wicket ................................................ SUCCESS [
> 0.883s]
> [INFO] Wicket Extensions ..................................... SUCCESS [
> 0.711s]
> [INFO] Wicket Spring Integration ............................. SUCCESS [
> 0.958s]
> [INFO] Wicket Quickstart ..................................... SUCCESS [
> 1.380s]
> [INFO] Wicket Date/Time ...................................... SUCCESS [
> 0.619s]
> [INFO] Wicket JDK 1.5 modules ................................ SUCCESS [
> 0.100s]
> [INFO] Wicket Auth Roles ..................................... SUCCESS [
> 0.224s]
> [INFO] Wicket Authorization Roles examples ................... SUCCESS [
> 0.316s]
> [INFO] Wicket JMX ............................................ SUCCESS [
> 0.282s]
> [INFO] Wicket Examples ....................................... SUCCESS [
> 2.895s]
> [INFO] Wicket Objects Sizeof Agent ........................... SUCCESS [
> 0.548s]
> [INFO] Wicket Portlet Examples ............................... SUCCESS [
> 0.396s]
> [INFO] Wicket Spring Integration through Annotations ......... SUCCESS [
> 0.377s]
> [INFO] Wicket Spring Annot Examples .......................... SUCCESS [
> 0.589s]
> [INFO] Wicket Spring Integration Examples .................... SUCCESS [
> 0.344s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 19 seconds
> [INFO] Finished at: Fri Mar 09 14:13:38 PST 2007
> [INFO] Final Memory: 14M/25M
> [INFO]
> ------------------------------------------------------------------------
>
> -igor
>
>
> On 3/9/07, Johan Compagner <jc...@gmail.com> wrote:
> >
> > What do you know exactly checkout?
> > this svn path?
> >
> >
> > /incubator/wicket/branches/al-test-wicket-1.3.x
> > But how are the project rooted then? (i haven't really looked at this but
> > eclipse doesn't support nested right?)
> >
> > johan
> >
> >
> > On 3/9/07, Al Maw <wi...@almaw.com> wrote:
> > >
> > > As detailed in the thread "almaw's new build-test branch" I've been
> > > thinking about how to make the release process work more smoothly.
> > >
> > > I've restructured how 1.3 is parented, etc. in the branch
> > > "al-test-wicket-1.3.x". You can see how it looks here:
> > >
> > >
> > http://svn.apache.org/viewvc/incubator/wicket/branches/al-test-wicket-1.3.x/
> > >
> > > Advantages:
> > > - It massively simplifies the pom.xml files and reduces redundancy and
> > > duplication, and removes the potential for the configuration of the
> > > various modules getting out of sync.
> > >
> > > - It's really obvious which projects need JDK 5 and which don't.
> > >
> > > - We will hopefully be able to use the Maven 2 release plug-in for
> > > the jdk-1.4 and jdk-1.5 bits and make everything more automated.
> > >
> > > - We don't need -P profile switches to build things any more.
> > >
> > > - Getting the whole shooting match into Eclipse is now:
> > > - One command to check it out.
> > > - One command to build the Eclipse .project, etc. files.
> > > - Three clicks in Eclipse to import all the projects, which will
> > > then all depend on each other correctly.
> > >
> > > - Removes the wicket-parent project, which is a bit mystical and lots
> > > of people don't discover by themselves.
> > >
> > >
> > > Disadvantages:
> > > - Everyone will need to update their workspaces.
> > >
> > >
> > > So, please vote:
> > > ================
> > >
> > > [ ] Yes, change the 1.x branch so it looks like that.
> > >
> > > [ ] No, don't restructure it! That's a rubbish idea!
> > >
> > >
> > > We could also take this opportunity to rename the 1.x branch to 1.3.x.
> > >
> > > If you voted yes above, please also vote:
> > > =========================================
> > >
> > > [ ] Yes, rename the branch to "wicket-1.3.x" at the same time so I
> > > only need to set my IDE workspace up again once.
> > >
> > > [ ] No, don't rename the branch, we'll postpone that until we
> > > release a beta, or a 1.3.0 final, or something.
> > >
> > > Given it's a bit of a faff for everyone, if this does go ahead I will
> > > post a time when I will move stuff at least a couple of days in advance
> > > so people can get their outstanding commits in, which should make it
> > > easy for everyone.
> > >
> > > If you were to have outstanding commits when things are moved, svn will
> > > keep the changes in orphaned files so you can move them across manually
> > > to the new layout. It's just a little less convenient.
> > >
> > > Al
> > >
> >
>
Re: VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Igor Vaynberg <ig...@gmail.com>.
mvn eclipse:eclipse in al-test-wicket-1.3.x does this :) one command builds
eclipse projects for everything that depend on each other rather then jars
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
------------------------------------------------------------------------
[INFO] Wicket Parent ......................................... SUCCESS [
4.854s]
[INFO] Wicket JDK 1.4 modules ................................ SUCCESS [
0.255s]
[INFO] Wicket ................................................ SUCCESS [
0.883s]
[INFO] Wicket Extensions ..................................... SUCCESS [
0.711s]
[INFO] Wicket Spring Integration ............................. SUCCESS [
0.958s]
[INFO] Wicket Quickstart ..................................... SUCCESS [
1.380s]
[INFO] Wicket Date/Time ...................................... SUCCESS [
0.619s]
[INFO] Wicket JDK 1.5 modules ................................ SUCCESS [
0.100s]
[INFO] Wicket Auth Roles ..................................... SUCCESS [
0.224s]
[INFO] Wicket Authorization Roles examples ................... SUCCESS [
0.316s]
[INFO] Wicket JMX ............................................ SUCCESS [
0.282s]
[INFO] Wicket Examples ....................................... SUCCESS [
2.895s]
[INFO] Wicket Objects Sizeof Agent ........................... SUCCESS [
0.548s]
[INFO] Wicket Portlet Examples ............................... SUCCESS [
0.396s]
[INFO] Wicket Spring Integration through Annotations ......... SUCCESS [
0.377s]
[INFO] Wicket Spring Annot Examples .......................... SUCCESS [
0.589s]
[INFO] Wicket Spring Integration Examples .................... SUCCESS [
0.344s]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 19 seconds
[INFO] Finished at: Fri Mar 09 14:13:38 PST 2007
[INFO] Final Memory: 14M/25M
[INFO]
------------------------------------------------------------------------
-igor
On 3/9/07, Johan Compagner <jc...@gmail.com> wrote:
>
> What do you know exactly checkout?
> this svn path?
>
>
> /incubator/wicket/branches/al-test-wicket-1.3.x
> But how are the project rooted then? (i haven't really looked at this but
> eclipse doesn't support nested right?)
>
> johan
>
>
> On 3/9/07, Al Maw <wi...@almaw.com> wrote:
> >
> > As detailed in the thread "almaw's new build-test branch" I've been
> > thinking about how to make the release process work more smoothly.
> >
> > I've restructured how 1.3 is parented, etc. in the branch
> > "al-test-wicket-1.3.x". You can see how it looks here:
> >
> >
> http://svn.apache.org/viewvc/incubator/wicket/branches/al-test-wicket-1.3.x/
> >
> > Advantages:
> > - It massively simplifies the pom.xml files and reduces redundancy and
> > duplication, and removes the potential for the configuration of the
> > various modules getting out of sync.
> >
> > - It's really obvious which projects need JDK 5 and which don't.
> >
> > - We will hopefully be able to use the Maven 2 release plug-in for
> > the jdk-1.4 and jdk-1.5 bits and make everything more automated.
> >
> > - We don't need -P profile switches to build things any more.
> >
> > - Getting the whole shooting match into Eclipse is now:
> > - One command to check it out.
> > - One command to build the Eclipse .project, etc. files.
> > - Three clicks in Eclipse to import all the projects, which will
> > then all depend on each other correctly.
> >
> > - Removes the wicket-parent project, which is a bit mystical and lots
> > of people don't discover by themselves.
> >
> >
> > Disadvantages:
> > - Everyone will need to update their workspaces.
> >
> >
> > So, please vote:
> > ================
> >
> > [ ] Yes, change the 1.x branch so it looks like that.
> >
> > [ ] No, don't restructure it! That's a rubbish idea!
> >
> >
> > We could also take this opportunity to rename the 1.x branch to 1.3.x.
> >
> > If you voted yes above, please also vote:
> > =========================================
> >
> > [ ] Yes, rename the branch to "wicket-1.3.x" at the same time so I
> > only need to set my IDE workspace up again once.
> >
> > [ ] No, don't rename the branch, we'll postpone that until we
> > release a beta, or a 1.3.0 final, or something.
> >
> > Given it's a bit of a faff for everyone, if this does go ahead I will
> > post a time when I will move stuff at least a couple of days in advance
> > so people can get their outstanding commits in, which should make it
> > easy for everyone.
> >
> > If you were to have outstanding commits when things are moved, svn will
> > keep the changes in orphaned files so you can move them across manually
> > to the new layout. It's just a little less convenient.
> >
> > Al
> >
>
Re: VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Johan Compagner <jc...@gmail.com>.
What do you know exactly checkout?
this svn path?
/incubator/wicket/branches/al-test-wicket-1.3.x
But how are the project rooted then? (i haven't really looked at this but
eclipse doesn't support nested right?)
johan
On 3/9/07, Al Maw <wi...@almaw.com> wrote:
>
> As detailed in the thread "almaw's new build-test branch" I've been
> thinking about how to make the release process work more smoothly.
>
> I've restructured how 1.3 is parented, etc. in the branch
> "al-test-wicket-1.3.x". You can see how it looks here:
>
> http://svn.apache.org/viewvc/incubator/wicket/branches/al-test-wicket-1.3.x/
>
> Advantages:
> - It massively simplifies the pom.xml files and reduces redundancy and
> duplication, and removes the potential for the configuration of the
> various modules getting out of sync.
>
> - It's really obvious which projects need JDK 5 and which don't.
>
> - We will hopefully be able to use the Maven 2 release plug-in for
> the jdk-1.4 and jdk-1.5 bits and make everything more automated.
>
> - We don't need -P profile switches to build things any more.
>
> - Getting the whole shooting match into Eclipse is now:
> - One command to check it out.
> - One command to build the Eclipse .project, etc. files.
> - Three clicks in Eclipse to import all the projects, which will
> then all depend on each other correctly.
>
> - Removes the wicket-parent project, which is a bit mystical and lots
> of people don't discover by themselves.
>
>
> Disadvantages:
> - Everyone will need to update their workspaces.
>
>
> So, please vote:
> ================
>
> [ ] Yes, change the 1.x branch so it looks like that.
>
> [ ] No, don't restructure it! That's a rubbish idea!
>
>
> We could also take this opportunity to rename the 1.x branch to 1.3.x.
>
> If you voted yes above, please also vote:
> =========================================
>
> [ ] Yes, rename the branch to "wicket-1.3.x" at the same time so I
> only need to set my IDE workspace up again once.
>
> [ ] No, don't rename the branch, we'll postpone that until we
> release a beta, or a 1.3.0 final, or something.
>
> Given it's a bit of a faff for everyone, if this does go ahead I will
> post a time when I will move stuff at least a couple of days in advance
> so people can get their outstanding commits in, which should make it
> easy for everyone.
>
> If you were to have outstanding commits when things are moved, svn will
> keep the changes in orphaned files so you can move them across manually
> to the new layout. It's just a little less convenient.
>
> Al
>
Re: [Vote] VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Eelco Hillenius <ee...@gmail.com>.
Oh. I just never used it without.
On 3/9/07, Igor Vaynberg <ig...@gmail.com> wrote:
> afaik mvn eclipse:eclipse doesnt run tests, so no need for the -
> Dmaven.test....
Re: [Vote] VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Igor Vaynberg <ig...@gmail.com>.
afaik mvn eclipse:eclipse doesnt run tests, so no need for the -
Dmaven.test....
-igor
On 3/9/07, Eelco Hillenius <ee...@gmail.com> wrote:
>
> > well the checkout went great. i like that a lot. but for those of
> > us who are mortal enemies of maven most of the time, what is
> > the one command and what are the three clicks again? ;-)
>
> mvn eclipse:clean eclipse:eclipse -DdownloadSources=true -
> Dmaven.test.skip=true
>
> The clicks are in eclipse to import the projects.
>
> Eelco
>
Re: [Vote] VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Jean-Baptiste Quenot <jb...@apache.org>.
* Jonathan Locke:
>
> i got help on this on ##wicket, but it seems like we need this in
> ./build.{sh|bat} for newbies:
>
> mvn install -Dmaven.test.skip=true
> mvn eclipse:clean eclipse:eclipse -DdownloadSources=true
> -Dmaven.test.skip=true
Please remove -Dmaven.test.skip=true in both commands. The tests
are supposed to pass.
Also, I don't think it's a good idea to do the eclipse:clean part,
as this will remove .settings files that are versioned in our
repository.
See http://maven.apache.org/plugins/maven-eclipse-plugin/clean-mojo.html
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
Re: [Vote] VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Igor Vaynberg <ig...@gmail.com>.
when we make a release we dont need the -Dmaven.test.skip=true :)
-igor
On 3/9/07, Jonathan Locke <jo...@gmail.com> wrote:
>
>
>
> i got help on this on ##wicket, but it seems like we need this in
> ./build.{sh|bat} for newbies:
>
> mvn install -Dmaven.test.skip=true
> mvn eclipse:clean eclipse:eclipse -DdownloadSources=true
> -Dmaven.test.skip=true
>
> we can add any future magic there and not have to educate everyone on
> maven
> details until they need to learn for some other reason.
>
>
> Jonathan Locke wrote:
> >
> >
> > i get this:
> >
> > [INFO] Failed to resolve artifact.
> >
> > required artifacts missing:
> > org.apache.wicket:wicket:jar:1.3.0-incubating-SNAPSHOT
> >
> > maybe something magic almaw is doing that i don't know about yet?
> >
> >
> > Jonathan Locke wrote:
> >>
> >>
> >> could we stick that in a build.sh and build.bat file in the root of the
> >> project?
> >> even if that doesn't work on ALL systems, it should work on most and is
> >> self
> >> documenting for the rest.
> >>
> >>
> >> Eelco Hillenius wrote:
> >>>
> >>>> well the checkout went great. i like that a lot. but for those of
> >>>> us who are mortal enemies of maven most of the time, what is
> >>>> the one command and what are the three clicks again? ;-)
> >>>
> >>> mvn eclipse:clean eclipse:eclipse -DdownloadSources=true
> >>> -Dmaven.test.skip=true
> >>>
> >>> The clicks are in eclipse to import the projects.
> >>>
> >>> Eelco
> >>>
> >>>
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/VOTE%3A-Move-modules-around-to-make-releasing-easier-in-1.x-branch-%28and-rename-branch%29.-tf3375891.html#a9404988
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>
Re: [Vote] VOTE: Move modules around to make releasing easier in
1.x branch (and rename branch).
Posted by Jonathan Locke <jo...@gmail.com>.
i got help on this on ##wicket, but it seems like we need this in
./build.{sh|bat} for newbies:
mvn install -Dmaven.test.skip=true
mvn eclipse:clean eclipse:eclipse -DdownloadSources=true
-Dmaven.test.skip=true
we can add any future magic there and not have to educate everyone on maven
details until they need to learn for some other reason.
Jonathan Locke wrote:
>
>
> i get this:
>
> [INFO] Failed to resolve artifact.
>
> required artifacts missing:
> org.apache.wicket:wicket:jar:1.3.0-incubating-SNAPSHOT
>
> maybe something magic almaw is doing that i don't know about yet?
>
>
> Jonathan Locke wrote:
>>
>>
>> could we stick that in a build.sh and build.bat file in the root of the
>> project?
>> even if that doesn't work on ALL systems, it should work on most and is
>> self
>> documenting for the rest.
>>
>>
>> Eelco Hillenius wrote:
>>>
>>>> well the checkout went great. i like that a lot. but for those of
>>>> us who are mortal enemies of maven most of the time, what is
>>>> the one command and what are the three clicks again? ;-)
>>>
>>> mvn eclipse:clean eclipse:eclipse -DdownloadSources=true
>>> -Dmaven.test.skip=true
>>>
>>> The clicks are in eclipse to import the projects.
>>>
>>> Eelco
>>>
>>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/VOTE%3A-Move-modules-around-to-make-releasing-easier-in-1.x-branch-%28and-rename-branch%29.-tf3375891.html#a9404988
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: [Vote] VOTE: Move modules around to make releasing easier in
1.x branch (and rename branch).
Posted by Jonathan Locke <jo...@gmail.com>.
i get this:
[INFO] Failed to resolve artifact.
required artifacts missing:
org.apache.wicket:wicket:jar:1.3.0-incubating-SNAPSHOT
maybe something magic almaw is doing that i don't know about yet?
Jonathan Locke wrote:
>
>
> could we stick that in a build.sh and build.bat file in the root of the
> project?
> even if that doesn't work on ALL systems, it should work on most and is
> self
> documenting for the rest.
>
>
> Eelco Hillenius wrote:
>>
>>> well the checkout went great. i like that a lot. but for those of
>>> us who are mortal enemies of maven most of the time, what is
>>> the one command and what are the three clicks again? ;-)
>>
>> mvn eclipse:clean eclipse:eclipse -DdownloadSources=true
>> -Dmaven.test.skip=true
>>
>> The clicks are in eclipse to import the projects.
>>
>> Eelco
>>
>>
>
>
--
View this message in context: http://www.nabble.com/VOTE%3A-Move-modules-around-to-make-releasing-easier-in-1.x-branch-%28and-rename-branch%29.-tf3375891.html#a9404782
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: [Vote] VOTE: Move modules around to make releasing easier in
1.x branch (and rename branch).
Posted by Jonathan Locke <jo...@gmail.com>.
could we stick that in a build.sh and build.bat file in the root of the
project?
even if that doesn't work on ALL systems, it should work on most and is self
documenting for the rest.
Eelco Hillenius wrote:
>
>> well the checkout went great. i like that a lot. but for those of
>> us who are mortal enemies of maven most of the time, what is
>> the one command and what are the three clicks again? ;-)
>
> mvn eclipse:clean eclipse:eclipse -DdownloadSources=true
> -Dmaven.test.skip=true
>
> The clicks are in eclipse to import the projects.
>
> Eelco
>
>
--
View this message in context: http://www.nabble.com/VOTE%3A-Move-modules-around-to-make-releasing-easier-in-1.x-branch-%28and-rename-branch%29.-tf3375891.html#a9404746
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: [Vote] VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Eelco Hillenius <ee...@gmail.com>.
> well the checkout went great. i like that a lot. but for those of
> us who are mortal enemies of maven most of the time, what is
> the one command and what are the three clicks again? ;-)
mvn eclipse:clean eclipse:eclipse -DdownloadSources=true -Dmaven.test.skip=true
The clicks are in eclipse to import the projects.
Eelco
Re: [Vote] VOTE: Move modules around to make releasing easier in
1.x branch (and rename branch).
Posted by Jonathan Locke <jo...@gmail.com>.
well the checkout went great. i like that a lot. but for those of
us who are mortal enemies of maven most of the time, what is
the one command and what are the three clicks again? ;-)
Al Maw wrote:
>
> - Getting the whole shooting match into Eclipse is now:
> - One command to check it out.
> - One command to build the Eclipse .project, etc. files.
> - Three clicks in Eclipse to import all the projects, which will
> then all depend on each other correctly.
>
--
View this message in context: http://www.nabble.com/VOTE%3A-Move-modules-around-to-make-releasing-easier-in-1.x-branch-%28and-rename-branch%29.-tf3375891.html#a9404655
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Igor Vaynberg <ig...@gmail.com>.
>
> [x] Yes, change the 1.x branch so it looks like that.
>
> [x] Yes, rename the branch to "wicket-1.3.x" at the same time so I
> only need to set my IDE workspace up again once.
-igor
Re: VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Martijn Dashorst <ma...@gmail.com>.
I'm -0 on this one. However, I think we can do this and see where it
takes us, at least let it work for the 1.3-beta1-incubating release
and see if/how it improves the release.
In the very least it cleans up our pom's to a great extend. I only
want one thing changed: the root pom should have the same version as
the rest of the projects, because the dependencies and plugins are
release specific (i.e. bound to the era of the release). I don't
expect the root pom to live its own live, at least not with
dependencies and plugin configuration inside.
-1 on renaming the branch: it seems too soon to me. We decided on this
naming to get rid of what our 1.x and 2.x streams were. As we are
going to vote on the future of trunk, I'd say don't change it just now
but wait with any renaming change until we sorted that out.
Martijn
--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org
Re: VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Eelco Hillenius <ee...@gmail.com>.
On 3/9/07, Igor Vaynberg <ig...@gmail.com> wrote:
> we _rename_ it, meaning we only have branches-1.3.x and no branches-1.x
Yes, I understand that. My point is that as far as I remember is not
according to the deal we agreed upon before, which was to keep the
development version on 1.x until we put a branch into maintenance mode
and start working on another (so when we would start 1.4, we would
make 1.3.x and work on 1.x for 1.4).
Eelco
Re: VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Igor Vaynberg <ig...@gmail.com>.
we _rename_ it, meaning we only have branches-1.3.x and no branches-1.x
-igor
On 3/9/07, Eelco Hillenius <ee...@gmail.com> wrote:
>
> [ x ] Yes, change the 1.x branch so it looks like that.
>
> [ ] No, don't restructure it! That's a rubbish idea!
>
> >
> > We could also take this opportunity to rename the 1.x branch to 1.3.x.
>
> Are we ready for that yet? I don't care too much personally, but I
> thought the deal was to that when a release goes into maintenance
> mode. I'll wait for Martijn to vent his opinion.
>
> Eelco
>
Re: VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Eelco Hillenius <ee...@gmail.com>.
[ x ] Yes, change the 1.x branch so it looks like that.
[ ] No, don't restructure it! That's a rubbish idea!
>
> We could also take this opportunity to rename the 1.x branch to 1.3.x.
Are we ready for that yet? I don't care too much personally, but I
thought the deal was to that when a release goes into maintenance
mode. I'll wait for Martijn to vent his opinion.
Eelco
Re: [Vote] VOTE: Move modules around to make releasing easier in
1.x branch (and rename branch).
Posted by Jonathan Locke <jo...@gmail.com>.
okay. i'm +1 for this change. i'm also +1 to call it wicket-1.3.x.
unless there's some technical reason for the name, i'd also like
to see wicket-objectssizeof-agent called wicket-object-sizeof-agent.
this would be a bit more readable and more like the other project
names.
jon
igor.vaynberg wrote:
>
> the two jdk subfolders will go away once we switch to jdk5
>
> -igor
>
>
> On 3/9/07, Jonathan Locke <jo...@gmail.com> wrote:
>>
>>
>>
>> i love this. anything to make maven builds of wicket dirt simple is
>> great.
>>
>> however, i'm unsure about the impact of the jdk folders. what happens
>> when wicket-extensions and wicket-datetime get generified? do those
>> then move to the other folder? do we wind up with two wicket-extensions
>> projects over the long run or does generics backwards compat mean
>> wicket-extensions just moves to the 1.5 folder and disappears from 1.4?
>>
>>
>> Al Maw wrote:
>> >
>> > As detailed in the thread "almaw's new build-test branch" I've been
>> > thinking about how to make the release process work more smoothly.
>> >
>> > I've restructured how 1.3 is parented, etc. in the branch
>> > "al-test-wicket-1.3.x". You can see how it looks here:
>> >
>> http://svn.apache.org/viewvc/incubator/wicket/branches/al-test-wicket-1.3.x/
>> >
>> > Advantages:
>> > - It massively simplifies the pom.xml files and reduces redundancy
>> and
>> > duplication, and removes the potential for the configuration of the
>> > various modules getting out of sync.
>> >
>> > - It's really obvious which projects need JDK 5 and which don't.
>> >
>> > - We will hopefully be able to use the Maven 2 release plug-in for
>> > the jdk-1.4 and jdk-1.5 bits and make everything more automated.
>> >
>> > - We don't need -P profile switches to build things any more.
>> >
>> > - Getting the whole shooting match into Eclipse is now:
>> > - One command to check it out.
>> > - One command to build the Eclipse .project, etc. files.
>> > - Three clicks in Eclipse to import all the projects, which will
>> > then all depend on each other correctly.
>> >
>> > - Removes the wicket-parent project, which is a bit mystical and lots
>> > of people don't discover by themselves.
>> >
>> >
>> > Disadvantages:
>> > - Everyone will need to update their workspaces.
>> >
>> >
>> > So, please vote:
>> > ================
>> >
>> > [ ] Yes, change the 1.x branch so it looks like that.
>> >
>> > [ ] No, don't restructure it! That's a rubbish idea!
>> >
>> >
>> > We could also take this opportunity to rename the 1.x branch to 1.3.x.
>> >
>> > If you voted yes above, please also vote:
>> > =========================================
>> >
>> > [ ] Yes, rename the branch to "wicket-1.3.x" at the same time so I
>> > only need to set my IDE workspace up again once.
>> >
>> > [ ] No, don't rename the branch, we'll postpone that until we
>> > release a beta, or a 1.3.0 final, or something.
>> >
>> > Given it's a bit of a faff for everyone, if this does go ahead I will
>> > post a time when I will move stuff at least a couple of days in advance
>> > so people can get their outstanding commits in, which should make it
>> > easy for everyone.
>> >
>> > If you were to have outstanding commits when things are moved, svn will
>> > keep the changes in orphaned files so you can move them across manually
>> > to the new layout. It's just a little less convenient.
>> >
>> > Al
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/VOTE%3A-Move-modules-around-to-make-releasing-easier-in-1.x-branch-%28and-rename-branch%29.-tf3375891.html#a9404299
>> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/VOTE%3A-Move-modules-around-to-make-releasing-easier-in-1.x-branch-%28and-rename-branch%29.-tf3375891.html#a9404414
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: [Vote] VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Igor Vaynberg <ig...@gmail.com>.
the two jdk subfolders will go away once we switch to jdk5
-igor
On 3/9/07, Jonathan Locke <jo...@gmail.com> wrote:
>
>
>
> i love this. anything to make maven builds of wicket dirt simple is
> great.
>
> however, i'm unsure about the impact of the jdk folders. what happens
> when wicket-extensions and wicket-datetime get generified? do those
> then move to the other folder? do we wind up with two wicket-extensions
> projects over the long run or does generics backwards compat mean
> wicket-extensions just moves to the 1.5 folder and disappears from 1.4?
>
>
> Al Maw wrote:
> >
> > As detailed in the thread "almaw's new build-test branch" I've been
> > thinking about how to make the release process work more smoothly.
> >
> > I've restructured how 1.3 is parented, etc. in the branch
> > "al-test-wicket-1.3.x". You can see how it looks here:
> >
> http://svn.apache.org/viewvc/incubator/wicket/branches/al-test-wicket-1.3.x/
> >
> > Advantages:
> > - It massively simplifies the pom.xml files and reduces redundancy and
> > duplication, and removes the potential for the configuration of the
> > various modules getting out of sync.
> >
> > - It's really obvious which projects need JDK 5 and which don't.
> >
> > - We will hopefully be able to use the Maven 2 release plug-in for
> > the jdk-1.4 and jdk-1.5 bits and make everything more automated.
> >
> > - We don't need -P profile switches to build things any more.
> >
> > - Getting the whole shooting match into Eclipse is now:
> > - One command to check it out.
> > - One command to build the Eclipse .project, etc. files.
> > - Three clicks in Eclipse to import all the projects, which will
> > then all depend on each other correctly.
> >
> > - Removes the wicket-parent project, which is a bit mystical and lots
> > of people don't discover by themselves.
> >
> >
> > Disadvantages:
> > - Everyone will need to update their workspaces.
> >
> >
> > So, please vote:
> > ================
> >
> > [ ] Yes, change the 1.x branch so it looks like that.
> >
> > [ ] No, don't restructure it! That's a rubbish idea!
> >
> >
> > We could also take this opportunity to rename the 1.x branch to 1.3.x.
> >
> > If you voted yes above, please also vote:
> > =========================================
> >
> > [ ] Yes, rename the branch to "wicket-1.3.x" at the same time so I
> > only need to set my IDE workspace up again once.
> >
> > [ ] No, don't rename the branch, we'll postpone that until we
> > release a beta, or a 1.3.0 final, or something.
> >
> > Given it's a bit of a faff for everyone, if this does go ahead I will
> > post a time when I will move stuff at least a couple of days in advance
> > so people can get their outstanding commits in, which should make it
> > easy for everyone.
> >
> > If you were to have outstanding commits when things are moved, svn will
> > keep the changes in orphaned files so you can move them across manually
> > to the new layout. It's just a little less convenient.
> >
> > Al
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/VOTE%3A-Move-modules-around-to-make-releasing-easier-in-1.x-branch-%28and-rename-branch%29.-tf3375891.html#a9404299
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>
Re: [Vote] VOTE: Move modules around to make releasing easier in 1.x branch (and rename branch).
Posted by Johan Compagner <jc...@gmail.com>.
when the are getting generified then it is under a different branch
completely i guess.
johan
On 3/9/07, Jonathan Locke <jo...@gmail.com> wrote:
>
>
>
> i love this. anything to make maven builds of wicket dirt simple is
> great.
>
> however, i'm unsure about the impact of the jdk folders. what happens
> when wicket-extensions and wicket-datetime get generified? do those
> then move to the other folder? do we wind up with two wicket-extensions
> projects over the long run or does generics backwards compat mean
> wicket-extensions just moves to the 1.5 folder and disappears from 1.4?
>
>
> Al Maw wrote:
> >
> > As detailed in the thread "almaw's new build-test branch" I've been
> > thinking about how to make the release process work more smoothly.
> >
> > I've restructured how 1.3 is parented, etc. in the branch
> > "al-test-wicket-1.3.x". You can see how it looks here:
> >
> http://svn.apache.org/viewvc/incubator/wicket/branches/al-test-wicket-1.3.x/
> >
> > Advantages:
> > - It massively simplifies the pom.xml files and reduces redundancy and
> > duplication, and removes the potential for the configuration of the
> > various modules getting out of sync.
> >
> > - It's really obvious which projects need JDK 5 and which don't.
> >
> > - We will hopefully be able to use the Maven 2 release plug-in for
> > the jdk-1.4 and jdk-1.5 bits and make everything more automated.
> >
> > - We don't need -P profile switches to build things any more.
> >
> > - Getting the whole shooting match into Eclipse is now:
> > - One command to check it out.
> > - One command to build the Eclipse .project, etc. files.
> > - Three clicks in Eclipse to import all the projects, which will
> > then all depend on each other correctly.
> >
> > - Removes the wicket-parent project, which is a bit mystical and lots
> > of people don't discover by themselves.
> >
> >
> > Disadvantages:
> > - Everyone will need to update their workspaces.
> >
> >
> > So, please vote:
> > ================
> >
> > [ ] Yes, change the 1.x branch so it looks like that.
> >
> > [ ] No, don't restructure it! That's a rubbish idea!
> >
> >
> > We could also take this opportunity to rename the 1.x branch to 1.3.x.
> >
> > If you voted yes above, please also vote:
> > =========================================
> >
> > [ ] Yes, rename the branch to "wicket-1.3.x" at the same time so I
> > only need to set my IDE workspace up again once.
> >
> > [ ] No, don't rename the branch, we'll postpone that until we
> > release a beta, or a 1.3.0 final, or something.
> >
> > Given it's a bit of a faff for everyone, if this does go ahead I will
> > post a time when I will move stuff at least a couple of days in advance
> > so people can get their outstanding commits in, which should make it
> > easy for everyone.
> >
> > If you were to have outstanding commits when things are moved, svn will
> > keep the changes in orphaned files so you can move them across manually
> > to the new layout. It's just a little less convenient.
> >
> > Al
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/VOTE%3A-Move-modules-around-to-make-releasing-easier-in-1.x-branch-%28and-rename-branch%29.-tf3375891.html#a9404299
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>
Re: [Vote] VOTE: Move modules around to make releasing easier in
1.x branch (and rename branch).
Posted by Jonathan Locke <jo...@gmail.com>.
i love this. anything to make maven builds of wicket dirt simple is great.
however, i'm unsure about the impact of the jdk folders. what happens
when wicket-extensions and wicket-datetime get generified? do those
then move to the other folder? do we wind up with two wicket-extensions
projects over the long run or does generics backwards compat mean
wicket-extensions just moves to the 1.5 folder and disappears from 1.4?
Al Maw wrote:
>
> As detailed in the thread "almaw's new build-test branch" I've been
> thinking about how to make the release process work more smoothly.
>
> I've restructured how 1.3 is parented, etc. in the branch
> "al-test-wicket-1.3.x". You can see how it looks here:
> http://svn.apache.org/viewvc/incubator/wicket/branches/al-test-wicket-1.3.x/
>
> Advantages:
> - It massively simplifies the pom.xml files and reduces redundancy and
> duplication, and removes the potential for the configuration of the
> various modules getting out of sync.
>
> - It's really obvious which projects need JDK 5 and which don't.
>
> - We will hopefully be able to use the Maven 2 release plug-in for
> the jdk-1.4 and jdk-1.5 bits and make everything more automated.
>
> - We don't need -P profile switches to build things any more.
>
> - Getting the whole shooting match into Eclipse is now:
> - One command to check it out.
> - One command to build the Eclipse .project, etc. files.
> - Three clicks in Eclipse to import all the projects, which will
> then all depend on each other correctly.
>
> - Removes the wicket-parent project, which is a bit mystical and lots
> of people don't discover by themselves.
>
>
> Disadvantages:
> - Everyone will need to update their workspaces.
>
>
> So, please vote:
> ================
>
> [ ] Yes, change the 1.x branch so it looks like that.
>
> [ ] No, don't restructure it! That's a rubbish idea!
>
>
> We could also take this opportunity to rename the 1.x branch to 1.3.x.
>
> If you voted yes above, please also vote:
> =========================================
>
> [ ] Yes, rename the branch to "wicket-1.3.x" at the same time so I
> only need to set my IDE workspace up again once.
>
> [ ] No, don't rename the branch, we'll postpone that until we
> release a beta, or a 1.3.0 final, or something.
>
> Given it's a bit of a faff for everyone, if this does go ahead I will
> post a time when I will move stuff at least a couple of days in advance
> so people can get their outstanding commits in, which should make it
> easy for everyone.
>
> If you were to have outstanding commits when things are moved, svn will
> keep the changes in orphaned files so you can move them across manually
> to the new layout. It's just a little less convenient.
>
> Al
>
>
--
View this message in context: http://www.nabble.com/VOTE%3A-Move-modules-around-to-make-releasing-easier-in-1.x-branch-%28and-rename-branch%29.-tf3375891.html#a9404299
Sent from the Wicket - Dev mailing list archive at Nabble.com.