You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Erik van Oosten <e....@grons.nl> on 2009/08/12 10:16:59 UTC
Wicketstuff releases?
Hello,
Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should I
use 1.4-rc8-SNAPSHOT?
I guess http://sourceforge.net/projects/wicket-stuff/files/ is no longer in
use.
Regards,
Erik.
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff core 1.4.0 release preparations
Posted by Erik van Oosten <e....@grons.nl>.
Yes, that did it. Running the dryRun in
wicket-stuff/wicketstuff-core/yui-parent/yui succeeds. I repeated this
for yui-examples.
yui-parent, yui and yui-examples are ready to go!
Regards,
Erik.
Erik van Oosten wrote:
> There is actually one more thing I could have tried: execute the
> release:prepare goals in de yui sub-sub modules.
>
>
> Igor Vaynberg wrote:
>> mvn clean package release:prepare -DdryRun=true
>>
>> -igor
>>
>> On Thu, Aug 13, 2009 at 8:33 AM, Erik van
>> Oosten<e....@grons.nl> wrote:
>>
>>> Hi Jeremy,
>>>
>>> I am afraid I do not understand what to do. I set out to test the
>>> yui-parent
>>> module:
>>>
>>> I can confirm that /yui-parent/ builds fine (with +mvn install+). Yeah!
>>>
>>> However, +mvn release:prepare -DdryRun=true+ executed in the yui-parent
>>> sub-directory just downloads a yui snapshot instead of compiling it
>>> localy.
>>> Running it one directory up fails because prepare:release does not
>>> accept
>>> diffs with the SCM and I changed the wicketstuff-code pom (I
>>> commented out
>>> all modules except for yui-parent).
>>>
>>> What else can I do? Or must one do the whole thing at once?
>>>
>>> BTW, should wicketstuff-core not change from 1.4-SNAPSHOT to
>>> 1.4.0-SNAPSHOT?
>>>
>>> Regards,
>>> Erik.
>>>
>>>
>
>
--
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff core 1.4.0 release preparations
Posted by Erik van Oosten <e....@grons.nl>.
Igor,
release:prepare automatically also does clean and package.
There is actually one more thing I could have tried: execute the
release:prepare goals in de yui sub-sub modules.
Regards,
Erik.
Igor Vaynberg wrote:
> mvn clean package release:prepare -DdryRun=true
>
> -igor
>
> On Thu, Aug 13, 2009 at 8:33 AM, Erik van Oosten<e....@grons.nl> wrote:
>
>> Hi Jeremy,
>>
>> I am afraid I do not understand what to do. I set out to test the yui-parent
>> module:
>>
>> I can confirm that /yui-parent/ builds fine (with +mvn install+). Yeah!
>>
>> However, +mvn release:prepare -DdryRun=true+ executed in the yui-parent
>> sub-directory just downloads a yui snapshot instead of compiling it localy.
>> Running it one directory up fails because prepare:release does not accept
>> diffs with the SCM and I changed the wicketstuff-code pom (I commented out
>> all modules except for yui-parent).
>>
>> What else can I do? Or must one do the whole thing at once?
>>
>> BTW, should wicketstuff-core not change from 1.4-SNAPSHOT to 1.4.0-SNAPSHOT?
>>
>> Regards,
>> Erik.
>>
>>
--
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff core 1.4.0 release preparations
Posted by Igor Vaynberg <ig...@gmail.com>.
mvn clean package release:prepare -DdryRun=true
-igor
On Thu, Aug 13, 2009 at 8:33 AM, Erik van Oosten<e....@grons.nl> wrote:
> Hi Jeremy,
>
> I am afraid I do not understand what to do. I set out to test the yui-parent
> module:
>
> I can confirm that /yui-parent/ builds fine (with +mvn install+). Yeah!
>
> However, +mvn release:prepare -DdryRun=true+ executed in the yui-parent
> sub-directory just downloads a yui snapshot instead of compiling it localy.
> Running it one directory up fails because prepare:release does not accept
> diffs with the SCM and I changed the wicketstuff-code pom (I commented out
> all modules except for yui-parent).
>
> What else can I do? Or must one do the whole thing at once?
>
> BTW, should wicketstuff-core not change from 1.4-SNAPSHOT to 1.4.0-SNAPSHOT?
>
> Regards,
> Erik.
>
>
>
> Jeremy Thomerson wrote:
>>
>> To those who have written me volunteering to help: thank you. I will
>> try to do the release this weekend. Here's what you can do to help
>> before then.
>>
>> 1 - check out wicketstuff-core trunk
>> 2 - change the wicket dependencies from snapshot to 1.4.0 (note: only
>> do this locally - don't commit that change - since trunk should run on
>> trunk)
>> 3 - build it to make sure it all works
>> 4 - test the release process by doing following:
>>
>> mvn release:prepare -DdryRun=true
>>
>> If all of that is working fine (no build errors, etc), then let the
>> list know. That will make it much easier to do the release. And I'll
>> try to document the process so that someone else can perform the next
>> one easier.
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>>
>
> --
> Erik van Oosten
> http://day-to-day-stuff.blogspot.com/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff core 1.4.0 release preparations
Posted by Martijn Dashorst <ma...@gmail.com>.
The release:prepare will also check if there are no SNAPSHOT
dependencies IIRC, or turn them into timestamped dependencies. If mvn
install works, then yui-parent is good to go I think.
Martijn
On Thu, Aug 13, 2009 at 5:33 PM, Erik van Oosten<e....@grons.nl> wrote:
> Hi Jeremy,
>
> I am afraid I do not understand what to do. I set out to test the yui-parent
> module:
>
> I can confirm that /yui-parent/ builds fine (with +mvn install+). Yeah!
>
> However, +mvn release:prepare -DdryRun=true+ executed in the yui-parent
> sub-directory just downloads a yui snapshot instead of compiling it localy.
> Running it one directory up fails because prepare:release does not accept
> diffs with the SCM and I changed the wicketstuff-code pom (I commented out
> all modules except for yui-parent).
>
> What else can I do? Or must one do the whole thing at once?
>
> BTW, should wicketstuff-core not change from 1.4-SNAPSHOT to 1.4.0-SNAPSHOT?
>
> Regards,
> Erik.
>
>
>
> Jeremy Thomerson wrote:
>>
>> To those who have written me volunteering to help: thank you. I will
>> try to do the release this weekend. Here's what you can do to help
>> before then.
>>
>> 1 - check out wicketstuff-core trunk
>> 2 - change the wicket dependencies from snapshot to 1.4.0 (note: only
>> do this locally - don't commit that change - since trunk should run on
>> trunk)
>> 3 - build it to make sure it all works
>> 4 - test the release process by doing following:
>>
>> mvn release:prepare -DdryRun=true
>>
>> If all of that is working fine (no build errors, etc), then let the
>> list know. That will make it much easier to do the release. And I'll
>> try to document the process so that someone else can perform the next
>> one easier.
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>>
>
> --
> Erik van Oosten
> http://day-to-day-stuff.blogspot.com/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Wicketstuff core 1.4.0 release preparations
Posted by Erik van Oosten <e....@grons.nl>.
Hi Jeremy,
I am afraid I do not understand what to do. I set out to test the
yui-parent module:
I can confirm that /yui-parent/ builds fine (with +mvn install+). Yeah!
However, +mvn release:prepare -DdryRun=true+ executed in the yui-parent
sub-directory just downloads a yui snapshot instead of compiling it
localy. Running it one directory up fails because prepare:release does
not accept diffs with the SCM and I changed the wicketstuff-code pom (I
commented out all modules except for yui-parent).
What else can I do? Or must one do the whole thing at once?
BTW, should wicketstuff-core not change from 1.4-SNAPSHOT to 1.4.0-SNAPSHOT?
Regards,
Erik.
Jeremy Thomerson wrote:
> To those who have written me volunteering to help: thank you. I will
> try to do the release this weekend. Here's what you can do to help
> before then.
>
> 1 - check out wicketstuff-core trunk
> 2 - change the wicket dependencies from snapshot to 1.4.0 (note: only
> do this locally - don't commit that change - since trunk should run on
> trunk)
> 3 - build it to make sure it all works
> 4 - test the release process by doing following:
>
> mvn release:prepare -DdryRun=true
>
> If all of that is working fine (no build errors, etc), then let the
> list know. That will make it much easier to do the release. And I'll
> try to document the process so that someone else can perform the next
> one easier.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff core 1.4.0 release preparations
Posted by Maarten Bosteels <mb...@gmail.com>.
On Thu, Aug 13, 2009 at 8:46 PM, Erik van Oosten <e....@grons.nl>wrote:
> Maarten, you just beated me to it.
>
> Is the jazzyplugin still needed after your changes?
Hi Erik,
I did not try to remove the dependency, so it's still needed.
I just downloaded the jar and installed in my local maven repo.
Maarten
>
> Regards,
> Erik.
>
>
> Erik van Oosten wrote:
>
>> Hi,
>>
>> Unfortunately tinymce does /not/ compile. It fails with a missing
>> dependency to jazzyplugin:jazzyplugin:jar:0.2.1.
>>
>> Regards,
>> Erik.
>>
>>
>
> --
> Erik van Oosten
> http://www.day-to-day-stuff.blogspot.com/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Wicketstuff core 1.4.0 release preparations
Posted by Erik van Oosten <e....@grons.nl>.
Maarten, you just beated me to it.
Is the jazzyplugin still needed after your changes?
Regards,
Erik.
Erik van Oosten wrote:
> Hi,
>
> Unfortunately tinymce does /not/ compile. It fails with a missing
> dependency to jazzyplugin:jazzyplugin:jar:0.2.1.
>
> Regards,
> Erik.
>
--
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Wicketstuff core 1.4.0 release preparations
Posted by Erik van Oosten <e....@grons.nl>.
Hi,
Unfortunately tinymce does /not/ compile. It fails with a missing
dependency to jazzyplugin:jazzyplugin:jar:0.2.1.
Regards,
Erik.
Jeremy Thomerson wrote:
> To those who have written me volunteering to help: thank you. I will
> try to do the release this weekend. Here's what you can do to help
> before then.
>
> 1 - check out wicketstuff-core trunk
> 2 - change the wicket dependencies from snapshot to 1.4.0 (note: only
> do this locally - don't commit that change - since trunk should run on
> trunk)
> 3 - build it to make sure it all works
> 4 - test the release process by doing following:
>
> mvn release:prepare -DdryRun=true
>
> If all of that is working fine (no build errors, etc), then let the
> list know. That will make it much easier to do the release. And I'll
> try to document the process so that someone else can perform the next
> one easier.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
--
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by Dane Laverty <da...@gmail.com>.
I followed your instructions. When I ran the mvn release:prepare, I was
asked several dozen times about versions, to which I responded with whatever
Maven's default choice was. Then there was a lot more output, and finally it
failed with an OutOfMemoryError: PermGen space. I know that's not very
helpful to you -- do you know what I can do to increase the memory available
to Maven?
On Thu, Aug 13, 2009 at 6:21 AM, Jeremy Thomerson <jeremy@wickettraining.com
> wrote:
> To those who have written me volunteering to help: thank you. I will
> try to do the release this weekend. Here's what you can do to help
> before then.
>
> 1 - check out wicketstuff-core trunk
> 2 - change the wicket dependencies from snapshot to 1.4.0 (note: only
> do this locally - don't commit that change - since trunk should run on
> trunk)
> 3 - build it to make sure it all works
> 4 - test the release process by doing following:
>
> mvn release:prepare -DdryRun=true
>
> If all of that is working fine (no build errors, etc), then let the
> list know. That will make it much easier to do the release. And I'll
> try to document the process so that someone else can perform the next
> one easier.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Wed, Aug 12, 2009 at 7:27 PM, Jeremy
> Thomerson<je...@wickettraining.com> wrote:
> > The idea behind the matching release numbers was so that Wicket newbs
> > could more easily adopt the most commonly used and supported
> > wicketstuff projects into their projects. I would like to be able to
> > still have that. No compatibility matrix needed - if you are using
> > Wicket 1.4.1 - use WS 1.4.1. That being said, I think that the best
> > solution is that we have 1.4.1.X where X is our release number.
> >
> > The biggest problem is still what a hassle it is to build a release.
> > When I built rc8, it took a couple days because people had broken junk
> > in trunk, not followed pom conventions, etc. Plus, syncing the build
> > artifacts to the repo was a pain because it's not documented, and I'm
> > no maven guru.
> >
> > I haven't even had time to build 1.4.0 to match Wicket yet, and that
> > is arguably the most important one since we started WS Core.
> >
> > If someone would like to help by building 1.4.0 and documenting a
> > streamlined process, I would love it. I have been running a Continuum
> > server that was doing continuous builds as well. I think that we
> > could see about using the release process on Continuum to run mvn
> > release:deploy and automating releases. I just don't have time this
> > week, and probably won't next week.
> >
> > So - anyone volunteering?
> >
> > --
> > Jeremy Thomerson
> > http://www.wickettraining.com
> >
> >
> >
> >
> > On Wed, Aug 12, 2009 at 1:01 PM, nino martinez
> > wael<ni...@gmail.com> wrote:
> >> Hmm I believe with may way it should be possible todo both..
> >>
> >> However I don't much care what the releases are named its the quality
> >> that matters to me. No matter what the customer will blame me if
> >> something does not work, they don't care if its a 1.4, 1.4.1.1
> >> release snapshot or snafu:)
> >>
> >> Jeremy are doing a fine job. However feedback are always nice, I like
> >> to get that too from my wicketstuffings.
> >>
> >> -my two cents..
> >>
> >> 2009/8/12 Martijn Dashorst <ma...@gmail.com>:
> >>> Given the lackluster release history of Wicket Stuff, I'd suggest
> >>> going with whatever the only person able *AND* willing to cut releases
> >>> wants. In this case, that is Jeremy. If you don't want to follow the
> >>> general Wicket Stuff release processes, you're welcome to maintain
> >>> your own projects and release them at your own schedule.
> >>>
> >>> It doesn't make sense to me to go back on a decision that was made,
> >>> just because 2 folks think it is "better". IMO having a release
> >>> following Wicket's releases is better than not having a release.
> >>>
> >>> The problem with Wicket Stuff is not that they follow the Wicket
> >>> release cycle, it is that nobody gives a damn to cut releases. Jeremy
> >>> fixed that. If you think you can do better, don't put your project in
> >>> the Wicket Stuff parent group, but release the software on your own.
> >>>
> >>> Martijn
> >>>
> >>>
> >>> On Wed, Aug 12, 2009 at 3:36 PM, Reinhard
> >>> Nägele<re...@mgm-tp.com> wrote:
> >>>> I'd like to second Maartens point. Identical releases to Wicket itself
> would
> >>>> mean that it always depends on Wicket. Independent releases would not
> be
> >>>> possible. Bugs could not be fixed and new features could not be added
> >>>> without a new Wicket release. This doesn't really make sense to me.
> >>>>
> >>>> Reinhard
> >>>>
> >>>>
> >>>> Jeremy Thomerson schrieb:
> >>>>>>>
> >>>>>>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core
> version is
> >>>>>>> compatible. There is no 1.4.0 version of wicketstuff core (yet?).
> Should
> >>>>>>> I
> >>>>>>> use 1.4-rc8-SNAPSHOT?
> >>>>>>>
> >>>>>
> >>>>> It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental
> >>>>> relic of after I built rc8
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> Side note: I don't see the version of wicket-stuff has to match
> exactly
> >>>>>> with version of wicket ?
> >>>>>> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow
> some
> >>>>>> bugs are fixed in wicketstuff-core, then we can't release these
> bug-fixes
> >>>>>> until wicket 1.4.1 is out ?
> >>>>>>
> >>>>>> IMO, wicket is just a dependency of wicketstuff-code (as defoined in
> the
> >>>>>> pom) and both projects should use their own unrelated version
> numbers.
> >>>>>>
> >>>>>> wdyt ?
> >>>>>>
> >>>>>
> >>>>> When I setup wicketstuff-core, I proposed that we structure it to
> have
> >>>>> identical releases to Wicket. The community agreed. I still think
> >>>>> this should be the case.
> >>>>> --
> >>>>> Jeremy Thomerson
> >>>>> http://www.wickettraining.com
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >>>>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >>>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Become a Wicket expert, learn from the best: http://wicketinaction.com
> >>> Apache Wicket 1.4 increases type safety for web applications
> >>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
RE: 1.4 ModalWindow closes on second submit attempt in FireFox
Posted by Stefan Lindner <li...@visionet.de>.
When I add each individual child oft he Form to the AjaxRequestTarget's Components by
Iterator<? extends Component> it = form.iterator();
while (it.hasNext())
Component c = it.next();
if (c.getOutputMarkupId() && c.isVisible())
target.addComponent(c);
Everything works too. So this could be a workaround for me. But is this the inteded way?
-----Ursprüngliche Nachricht-----
Von: Stefan Lindner [mailto:lindner@visionet.de]
Gesendet: Donnerstag, 13. August 2009 20:47
An: users@wicket.apache.org
Betreff: RE: 1.4 ModalWindow closes on second submit attempt in FireFox
After a little bit more investigation:
1. Now I use AjaxSubmitLink instead of AjaxButton.
--> same problem
2. I noticed that I have
@Override
protected void onError(final AjaxRequestTarget target, final Form<?> form) {
form.visitFormComponents(myInputfieldMarkerForInvalidInput);
target.addComponent(form);
}
--> If I don't call 'target.addComponent(form);' the problem disappears.
Is this a known problem? Is it forbidden to add a Form in a ModalWindow to an AjaxRequestTargets Components?
Stefan
-----Ursprüngliche Nachricht-----
Von: Stefan Lindner [mailto:lindner@visionet.de]
Gesendet: Donnerstag, 13. August 2009 20:14
An: users@wicket.apache.org
Betreff: 1.4 ModalWindow closes on second submit attempt in FireFox
I have a ModelWindow with a Panel containing a Form as content. When I submit the Form with an AjaxButton the first time everything is OK. Now when I click the AjaxSubmit a second time, FireFox wants to close the ModalWindow "Reloading this page will cause the modal window to disappear."
I found some hits on "Reloading this page will cause the modal window to disappear" but none of thme adresses FireFox.
The URL after the ModelWindow was closed is http://localhost:8080/VisioDesk/?id1a_hf_0=&name=&geplanterZeitpunktWoche=&wochentag=&dauerInMinuten%3AinputField=0&dauerInMinuten%3AselectField=&anfangUhrzeit=&ressourcen%3Aselect1=&ressourcen%3Aselect2=&personal%3Aselect1=&personal%3Aselect2=&submitButton=speichern
Any idea?
RE: 1.4 ModalWindow closes on second submit attempt in FireFox
Posted by Stefan Lindner <li...@visionet.de>.
After a little bit more investigation:
1. Now I use AjaxSubmitLink instead of AjaxButton.
--> same problem
2. I noticed that I have
@Override
protected void onError(final AjaxRequestTarget target, final Form<?> form) {
form.visitFormComponents(myInputfieldMarkerForInvalidInput);
target.addComponent(form);
}
--> If I don't call 'target.addComponent(form);' the problem disappears.
Is this a known problem? Is it forbidden to add a Form in a ModalWindow to an AjaxRequestTargets Components?
Stefan
-----Ursprüngliche Nachricht-----
Von: Stefan Lindner [mailto:lindner@visionet.de]
Gesendet: Donnerstag, 13. August 2009 20:14
An: users@wicket.apache.org
Betreff: 1.4 ModalWindow closes on second submit attempt in FireFox
I have a ModelWindow with a Panel containing a Form as content. When I submit the Form with an AjaxButton the first time everything is OK. Now when I click the AjaxSubmit a second time, FireFox wants to close the ModalWindow "Reloading this page will cause the modal window to disappear."
I found some hits on "Reloading this page will cause the modal window to disappear" but none of thme adresses FireFox.
The URL after the ModelWindow was closed is http://localhost:8080/VisioDesk/?id1a_hf_0=&name=&geplanterZeitpunktWoche=&wochentag=&dauerInMinuten%3AinputField=0&dauerInMinuten%3AselectField=&anfangUhrzeit=&ressourcen%3Aselect1=&ressourcen%3Aselect2=&personal%3Aselect1=&personal%3Aselect2=&submitButton=speichern
Any idea?
1.4 ModalWindow closes on second submit attempt in FireFox
Posted by Stefan Lindner <li...@visionet.de>.
I have a ModelWindow with a Panel containing a Form as content. When I submit the Form with an AjaxButton the first time everything is OK. Now when I click the AjaxSubmit a second time, FireFox wants to close the ModalWindow "Reloading this page will cause the modal window to disappear."
I found some hits on "Reloading this page will cause the modal window to disappear" but none of thme adresses FireFox.
The URL after the ModelWindow was closed is http://localhost:8080/VisioDesk/?id1a_hf_0=&name=&geplanterZeitpunktWoche=&wochentag=&dauerInMinuten%3AinputField=0&dauerInMinuten%3AselectField=&anfangUhrzeit=&ressourcen%3Aselect1=&ressourcen%3Aselect2=&personal%3Aselect1=&personal%3Aselect2=&submitButton=speichern
Any idea?
Re: Wicketstuff releases?
Posted by Maarten Bosteels <mb...@gmail.com>.
Hi,
svn co
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/sandbox/maarten/wicketstuff-core-1.4.0.0/
mvn clean package release:prepare -DdryRun=true -DreleaseVersion=1.4.0.0
-DdevelopmentVersion=1.4.0.1-SNAPSHOT
=> BUILD SUCCESSFUL
Let me know if I can test something else.
Maarten
On Thu, Aug 13, 2009 at 7:18 PM, Maarten Bosteels
<mb...@gmail.com>wrote:
> Hi,
>
> Revision: 4896
>
> After manually installing jazzyplugin from [1] into my local maven repo, I
> had the following results:
>
> mvn clean install => BUILD SUCCESSFUL
>
> mvn clean package release:prepare -DdryRun=true
>
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Cannot prepare the release because you have local modifications :
> [pom.xml:modified]
> [multi-text-input-parent/pom.xml:modified]
>
> I will create a branch in sandbox, commit changes to wicket.version and try
> again
>
> [1]
> http://prdownloads.sourceforge.net/jedit-plugins/JazzyPlugin-0.2.1-bin.zip
>
> regards,
> Maarten
>
>
> On Thu, Aug 13, 2009 at 5:16 PM, Erik van Oosten <e....@grons.nl>wrote:
>
>> Regarding step 2: only change the dependency to Wicket in the
>> wicketstuff-core pom.xml, not the versions of wicketstuff poms themselfs (as
>> I just did).
>>
>> Regards,
>> Erik.
>>
>>
>> Jeremy Thomerson wrote:
>>
>>> To those who have written me volunteering to help: thank you. I will
>>> try to do the release this weekend. Here's what you can do to help
>>> before then.
>>>
>>> 1 - check out wicketstuff-core trunk
>>> 2 - change the wicket dependencies from snapshot to 1.4.0 (note: only
>>> do this locally - don't commit that change - since trunk should run on
>>> trunk)
>>> 3 - build it to make sure it all works
>>> 4 - test the release process by doing following:
>>>
>>> mvn release:prepare -DdryRun=true
>>>
>>> If all of that is working fine (no build errors, etc), then let the
>>> list know. That will make it much easier to do the release. And I'll
>>> try to document the process so that someone else can perform the next
>>> one easier.
>>>
>>> --
>>> Jeremy Thomerson
>>> http://www.wickettraining.com
>>>
>>>
>> --
>> Erik van Oosten
>> http://day-to-day-stuff.blogspot.com/
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
Re: Wicketstuff releases?
Posted by Maarten Bosteels <mb...@gmail.com>.
Hi,
Revision: 4896
After manually installing jazzyplugin from [1] into my local maven repo, I
had the following results:
mvn clean install => BUILD SUCCESSFUL
mvn clean package release:prepare -DdryRun=true
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Cannot prepare the release because you have local modifications :
[pom.xml:modified]
[multi-text-input-parent/pom.xml:modified]
I will create a branch in sandbox, commit changes to wicket.version and try
again
[1]
http://prdownloads.sourceforge.net/jedit-plugins/JazzyPlugin-0.2.1-bin.zip
regards,
Maarten
On Thu, Aug 13, 2009 at 5:16 PM, Erik van Oosten <e....@grons.nl>wrote:
> Regarding step 2: only change the dependency to Wicket in the
> wicketstuff-core pom.xml, not the versions of wicketstuff poms themselfs (as
> I just did).
>
> Regards,
> Erik.
>
>
> Jeremy Thomerson wrote:
>
>> To those who have written me volunteering to help: thank you. I will
>> try to do the release this weekend. Here's what you can do to help
>> before then.
>>
>> 1 - check out wicketstuff-core trunk
>> 2 - change the wicket dependencies from snapshot to 1.4.0 (note: only
>> do this locally - don't commit that change - since trunk should run on
>> trunk)
>> 3 - build it to make sure it all works
>> 4 - test the release process by doing following:
>>
>> mvn release:prepare -DdryRun=true
>>
>> If all of that is working fine (no build errors, etc), then let the
>> list know. That will make it much easier to do the release. And I'll
>> try to document the process so that someone else can perform the next
>> one easier.
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>>
> --
> Erik van Oosten
> http://day-to-day-stuff.blogspot.com/
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Wicketstuff releases?
Posted by Erik van Oosten <e....@grons.nl>.
Regarding step 2: only change the dependency to Wicket in the
wicketstuff-core pom.xml, not the versions of wicketstuff poms themselfs
(as I just did).
Regards,
Erik.
Jeremy Thomerson wrote:
> To those who have written me volunteering to help: thank you. I will
> try to do the release this weekend. Here's what you can do to help
> before then.
>
> 1 - check out wicketstuff-core trunk
> 2 - change the wicket dependencies from snapshot to 1.4.0 (note: only
> do this locally - don't commit that change - since trunk should run on
> trunk)
> 3 - build it to make sure it all works
> 4 - test the release process by doing following:
>
> mvn release:prepare -DdryRun=true
>
> If all of that is working fine (no build errors, etc), then let the
> list know. That will make it much easier to do the release. And I'll
> try to document the process so that someone else can perform the next
> one easier.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by Jeremy Thomerson <je...@wickettraining.com>.
To those who have written me volunteering to help: thank you. I will
try to do the release this weekend. Here's what you can do to help
before then.
1 - check out wicketstuff-core trunk
2 - change the wicket dependencies from snapshot to 1.4.0 (note: only
do this locally - don't commit that change - since trunk should run on
trunk)
3 - build it to make sure it all works
4 - test the release process by doing following:
mvn release:prepare -DdryRun=true
If all of that is working fine (no build errors, etc), then let the
list know. That will make it much easier to do the release. And I'll
try to document the process so that someone else can perform the next
one easier.
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Aug 12, 2009 at 7:27 PM, Jeremy
Thomerson<je...@wickettraining.com> wrote:
> The idea behind the matching release numbers was so that Wicket newbs
> could more easily adopt the most commonly used and supported
> wicketstuff projects into their projects. I would like to be able to
> still have that. No compatibility matrix needed - if you are using
> Wicket 1.4.1 - use WS 1.4.1. That being said, I think that the best
> solution is that we have 1.4.1.X where X is our release number.
>
> The biggest problem is still what a hassle it is to build a release.
> When I built rc8, it took a couple days because people had broken junk
> in trunk, not followed pom conventions, etc. Plus, syncing the build
> artifacts to the repo was a pain because it's not documented, and I'm
> no maven guru.
>
> I haven't even had time to build 1.4.0 to match Wicket yet, and that
> is arguably the most important one since we started WS Core.
>
> If someone would like to help by building 1.4.0 and documenting a
> streamlined process, I would love it. I have been running a Continuum
> server that was doing continuous builds as well. I think that we
> could see about using the release process on Continuum to run mvn
> release:deploy and automating releases. I just don't have time this
> week, and probably won't next week.
>
> So - anyone volunteering?
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Wed, Aug 12, 2009 at 1:01 PM, nino martinez
> wael<ni...@gmail.com> wrote:
>> Hmm I believe with may way it should be possible todo both..
>>
>> However I don't much care what the releases are named its the quality
>> that matters to me. No matter what the customer will blame me if
>> something does not work, they don't care if its a 1.4, 1.4.1.1
>> release snapshot or snafu:)
>>
>> Jeremy are doing a fine job. However feedback are always nice, I like
>> to get that too from my wicketstuffings.
>>
>> -my two cents..
>>
>> 2009/8/12 Martijn Dashorst <ma...@gmail.com>:
>>> Given the lackluster release history of Wicket Stuff, I'd suggest
>>> going with whatever the only person able *AND* willing to cut releases
>>> wants. In this case, that is Jeremy. If you don't want to follow the
>>> general Wicket Stuff release processes, you're welcome to maintain
>>> your own projects and release them at your own schedule.
>>>
>>> It doesn't make sense to me to go back on a decision that was made,
>>> just because 2 folks think it is "better". IMO having a release
>>> following Wicket's releases is better than not having a release.
>>>
>>> The problem with Wicket Stuff is not that they follow the Wicket
>>> release cycle, it is that nobody gives a damn to cut releases. Jeremy
>>> fixed that. If you think you can do better, don't put your project in
>>> the Wicket Stuff parent group, but release the software on your own.
>>>
>>> Martijn
>>>
>>>
>>> On Wed, Aug 12, 2009 at 3:36 PM, Reinhard
>>> Nägele<re...@mgm-tp.com> wrote:
>>>> I'd like to second Maartens point. Identical releases to Wicket itself would
>>>> mean that it always depends on Wicket. Independent releases would not be
>>>> possible. Bugs could not be fixed and new features could not be added
>>>> without a new Wicket release. This doesn't really make sense to me.
>>>>
>>>> Reinhard
>>>>
>>>>
>>>> Jeremy Thomerson schrieb:
>>>>>>>
>>>>>>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
>>>>>>> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should
>>>>>>> I
>>>>>>> use 1.4-rc8-SNAPSHOT?
>>>>>>>
>>>>>
>>>>> It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental
>>>>> relic of after I built rc8
>>>>>
>>>>>
>>>>>>
>>>>>> Side note: I don't see the version of wicket-stuff has to match exactly
>>>>>> with version of wicket ?
>>>>>> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
>>>>>> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
>>>>>> until wicket 1.4.1 is out ?
>>>>>>
>>>>>> IMO, wicket is just a dependency of wicketstuff-code (as defoined in the
>>>>>> pom) and both projects should use their own unrelated version numbers.
>>>>>>
>>>>>> wdyt ?
>>>>>>
>>>>>
>>>>> When I setup wicketstuff-core, I proposed that we structure it to have
>>>>> identical releases to Wicket. The community agreed. I still think
>>>>> this should be the case.
>>>>> --
>>>>> Jeremy Thomerson
>>>>> http://www.wickettraining.com
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>>> Apache Wicket 1.4 increases type safety for web applications
>>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by nino martinez wael <ni...@gmail.com>.
Yeah I think too that 1.4.1.X is the best.
I'd be happy to volunteer but am swamped with work. Thanks for the
good work so far..
regards Nino
2009/8/13 Jeremy Thomerson <je...@wickettraining.com>:
> The idea behind the matching release numbers was so that Wicket newbs
> could more easily adopt the most commonly used and supported
> wicketstuff projects into their projects. I would like to be able to
> still have that. No compatibility matrix needed - if you are using
> Wicket 1.4.1 - use WS 1.4.1. That being said, I think that the best
> solution is that we have 1.4.1.X where X is our release number.
>
> The biggest problem is still what a hassle it is to build a release.
> When I built rc8, it took a couple days because people had broken junk
> in trunk, not followed pom conventions, etc. Plus, syncing the build
> artifacts to the repo was a pain because it's not documented, and I'm
> no maven guru.
>
> I haven't even had time to build 1.4.0 to match Wicket yet, and that
> is arguably the most important one since we started WS Core.
>
> If someone would like to help by building 1.4.0 and documenting a
> streamlined process, I would love it. I have been running a Continuum
> server that was doing continuous builds as well. I think that we
> could see about using the release process on Continuum to run mvn
> release:deploy and automating releases. I just don't have time this
> week, and probably won't next week.
>
> So - anyone volunteering?
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Wed, Aug 12, 2009 at 1:01 PM, nino martinez
> wael<ni...@gmail.com> wrote:
>> Hmm I believe with may way it should be possible todo both..
>>
>> However I don't much care what the releases are named its the quality
>> that matters to me. No matter what the customer will blame me if
>> something does not work, they don't care if its a 1.4, 1.4.1.1
>> release snapshot or snafu:)
>>
>> Jeremy are doing a fine job. However feedback are always nice, I like
>> to get that too from my wicketstuffings.
>>
>> -my two cents..
>>
>> 2009/8/12 Martijn Dashorst <ma...@gmail.com>:
>>> Given the lackluster release history of Wicket Stuff, I'd suggest
>>> going with whatever the only person able *AND* willing to cut releases
>>> wants. In this case, that is Jeremy. If you don't want to follow the
>>> general Wicket Stuff release processes, you're welcome to maintain
>>> your own projects and release them at your own schedule.
>>>
>>> It doesn't make sense to me to go back on a decision that was made,
>>> just because 2 folks think it is "better". IMO having a release
>>> following Wicket's releases is better than not having a release.
>>>
>>> The problem with Wicket Stuff is not that they follow the Wicket
>>> release cycle, it is that nobody gives a damn to cut releases. Jeremy
>>> fixed that. If you think you can do better, don't put your project in
>>> the Wicket Stuff parent group, but release the software on your own.
>>>
>>> Martijn
>>>
>>>
>>> On Wed, Aug 12, 2009 at 3:36 PM, Reinhard
>>> Nägele<re...@mgm-tp.com> wrote:
>>>> I'd like to second Maartens point. Identical releases to Wicket itself would
>>>> mean that it always depends on Wicket. Independent releases would not be
>>>> possible. Bugs could not be fixed and new features could not be added
>>>> without a new Wicket release. This doesn't really make sense to me.
>>>>
>>>> Reinhard
>>>>
>>>>
>>>> Jeremy Thomerson schrieb:
>>>>>>>
>>>>>>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
>>>>>>> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should
>>>>>>> I
>>>>>>> use 1.4-rc8-SNAPSHOT?
>>>>>>>
>>>>>
>>>>> It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental
>>>>> relic of after I built rc8
>>>>>
>>>>>
>>>>>>
>>>>>> Side note: I don't see the version of wicket-stuff has to match exactly
>>>>>> with version of wicket ?
>>>>>> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
>>>>>> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
>>>>>> until wicket 1.4.1 is out ?
>>>>>>
>>>>>> IMO, wicket is just a dependency of wicketstuff-code (as defoined in the
>>>>>> pom) and both projects should use their own unrelated version numbers.
>>>>>>
>>>>>> wdyt ?
>>>>>>
>>>>>
>>>>> When I setup wicketstuff-core, I proposed that we structure it to have
>>>>> identical releases to Wicket. The community agreed. I still think
>>>>> this should be the case.
>>>>> --
>>>>> Jeremy Thomerson
>>>>> http://www.wickettraining.com
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>>> Apache Wicket 1.4 increases type safety for web applications
>>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by Jeremy Thomerson <je...@wickettraining.com>.
The idea behind the matching release numbers was so that Wicket newbs
could more easily adopt the most commonly used and supported
wicketstuff projects into their projects. I would like to be able to
still have that. No compatibility matrix needed - if you are using
Wicket 1.4.1 - use WS 1.4.1. That being said, I think that the best
solution is that we have 1.4.1.X where X is our release number.
The biggest problem is still what a hassle it is to build a release.
When I built rc8, it took a couple days because people had broken junk
in trunk, not followed pom conventions, etc. Plus, syncing the build
artifacts to the repo was a pain because it's not documented, and I'm
no maven guru.
I haven't even had time to build 1.4.0 to match Wicket yet, and that
is arguably the most important one since we started WS Core.
If someone would like to help by building 1.4.0 and documenting a
streamlined process, I would love it. I have been running a Continuum
server that was doing continuous builds as well. I think that we
could see about using the release process on Continuum to run mvn
release:deploy and automating releases. I just don't have time this
week, and probably won't next week.
So - anyone volunteering?
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Aug 12, 2009 at 1:01 PM, nino martinez
wael<ni...@gmail.com> wrote:
> Hmm I believe with may way it should be possible todo both..
>
> However I don't much care what the releases are named its the quality
> that matters to me. No matter what the customer will blame me if
> something does not work, they don't care if its a 1.4, 1.4.1.1
> release snapshot or snafu:)
>
> Jeremy are doing a fine job. However feedback are always nice, I like
> to get that too from my wicketstuffings.
>
> -my two cents..
>
> 2009/8/12 Martijn Dashorst <ma...@gmail.com>:
>> Given the lackluster release history of Wicket Stuff, I'd suggest
>> going with whatever the only person able *AND* willing to cut releases
>> wants. In this case, that is Jeremy. If you don't want to follow the
>> general Wicket Stuff release processes, you're welcome to maintain
>> your own projects and release them at your own schedule.
>>
>> It doesn't make sense to me to go back on a decision that was made,
>> just because 2 folks think it is "better". IMO having a release
>> following Wicket's releases is better than not having a release.
>>
>> The problem with Wicket Stuff is not that they follow the Wicket
>> release cycle, it is that nobody gives a damn to cut releases. Jeremy
>> fixed that. If you think you can do better, don't put your project in
>> the Wicket Stuff parent group, but release the software on your own.
>>
>> Martijn
>>
>>
>> On Wed, Aug 12, 2009 at 3:36 PM, Reinhard
>> Nägele<re...@mgm-tp.com> wrote:
>>> I'd like to second Maartens point. Identical releases to Wicket itself would
>>> mean that it always depends on Wicket. Independent releases would not be
>>> possible. Bugs could not be fixed and new features could not be added
>>> without a new Wicket release. This doesn't really make sense to me.
>>>
>>> Reinhard
>>>
>>>
>>> Jeremy Thomerson schrieb:
>>>>>>
>>>>>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
>>>>>> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should
>>>>>> I
>>>>>> use 1.4-rc8-SNAPSHOT?
>>>>>>
>>>>
>>>> It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental
>>>> relic of after I built rc8
>>>>
>>>>
>>>>>
>>>>> Side note: I don't see the version of wicket-stuff has to match exactly
>>>>> with version of wicket ?
>>>>> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
>>>>> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
>>>>> until wicket 1.4.1 is out ?
>>>>>
>>>>> IMO, wicket is just a dependency of wicketstuff-code (as defoined in the
>>>>> pom) and both projects should use their own unrelated version numbers.
>>>>>
>>>>> wdyt ?
>>>>>
>>>>
>>>> When I setup wicketstuff-core, I proposed that we structure it to have
>>>> identical releases to Wicket. The community agreed. I still think
>>>> this should be the case.
>>>> --
>>>> Jeremy Thomerson
>>>> http://www.wickettraining.com
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.4 increases type safety for web applications
>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by nino martinez wael <ni...@gmail.com>.
Hmm I believe with may way it should be possible todo both..
However I don't much care what the releases are named its the quality
that matters to me. No matter what the customer will blame me if
something does not work, they don't care if its a 1.4, 1.4.1.1
release snapshot or snafu:)
Jeremy are doing a fine job. However feedback are always nice, I like
to get that too from my wicketstuffings.
-my two cents..
2009/8/12 Martijn Dashorst <ma...@gmail.com>:
> Given the lackluster release history of Wicket Stuff, I'd suggest
> going with whatever the only person able *AND* willing to cut releases
> wants. In this case, that is Jeremy. If you don't want to follow the
> general Wicket Stuff release processes, you're welcome to maintain
> your own projects and release them at your own schedule.
>
> It doesn't make sense to me to go back on a decision that was made,
> just because 2 folks think it is "better". IMO having a release
> following Wicket's releases is better than not having a release.
>
> The problem with Wicket Stuff is not that they follow the Wicket
> release cycle, it is that nobody gives a damn to cut releases. Jeremy
> fixed that. If you think you can do better, don't put your project in
> the Wicket Stuff parent group, but release the software on your own.
>
> Martijn
>
>
> On Wed, Aug 12, 2009 at 3:36 PM, Reinhard
> Nägele<re...@mgm-tp.com> wrote:
>> I'd like to second Maartens point. Identical releases to Wicket itself would
>> mean that it always depends on Wicket. Independent releases would not be
>> possible. Bugs could not be fixed and new features could not be added
>> without a new Wicket release. This doesn't really make sense to me.
>>
>> Reinhard
>>
>>
>> Jeremy Thomerson schrieb:
>>>>>
>>>>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
>>>>> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should
>>>>> I
>>>>> use 1.4-rc8-SNAPSHOT?
>>>>>
>>>
>>> It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental
>>> relic of after I built rc8
>>>
>>>
>>>>
>>>> Side note: I don't see the version of wicket-stuff has to match exactly
>>>> with version of wicket ?
>>>> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
>>>> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
>>>> until wicket 1.4.1 is out ?
>>>>
>>>> IMO, wicket is just a dependency of wicketstuff-code (as defoined in the
>>>> pom) and both projects should use their own unrelated version numbers.
>>>>
>>>> wdyt ?
>>>>
>>>
>>> When I setup wicketstuff-core, I proposed that we structure it to have
>>> identical releases to Wicket. The community agreed. I still think
>>> this should be the case.
>>> --
>>> Jeremy Thomerson
>>> http://www.wickettraining.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.4 increases type safety for web applications
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by Martijn Dashorst <ma...@gmail.com>.
Apparently my statements didn't provide the correct context. s/Wicket
Stuff/Wicket Stuff Core/g
I'm not talking about dropping code into sf.net's svn repository. I'm
talking about cutting releases. This is and has been a problem for
Wicket Stuff projects. Like it or not, Wicket Stuff as a whole is a
code dumping ground. Unless you release your code, it isn't finished.
I've yet to see consistent releases being performed by any of the
projects. My observation may be "Not constructive" but it is a fact.
The Wicket Stuff Core project is one of best things that happened to
Wicket Stuff, and I give Jeremy my fullest support in organizing those
projects in anyway he can. He has asked the community how to cut
releases. The community answered and the answer was to follow Wicket
releases. There's good reasoning behind this decision. There is little
to support the notion that more releases are necessary or even
warranted. Yes if your particular project inside Wicket Stuff Core has
a bug fix and the release takes a while it is a drag. But consider the
fact that if you have your code in good shape, you get releases *for
free*!
If you want to have your own release schedule, don't put your project
inside the Wicket Stuff Core projects, and go ahead to perform your
own releases. It's that simple. And if that is "my way or the highway"
then so be it. Wicket Stuff Core is for projects that want to adhere
to the Wicket Stuff Core rules, set forward by the guy that is
actually doing the work. Respect the time of the guy performing the
release, don't add unnecessary time or procedures to his schedule and
ensure your code is in optimal shape *ALWAYS*.
I find it much more constructive to enable Jeremy to have to jump
through as few hoops as possible, than to add more hoops. I don't like
to spend other people's free time. If you think that is "Not
Constructive" so be it.
Martijn
On Wed, Aug 12, 2009 at 5:49 PM, Maarten
Bosteels<mb...@gmail.com> wrote:
> Martijn,
>
> First off: I do appreciate the time and work that Jeremy spends on
> wicketstuff
>
>
> On Wed, Aug 12, 2009 at 4:05 PM, Martijn Dashorst <
> martijn.dashorst@gmail.com> wrote:
>
>> Given the lackluster release history of Wicket Stuff, I'd suggest
>> going with whatever the only person able *AND* willing to cut releases
>> wants. In this case, that is Jeremy. If you don't want to follow the
>> general Wicket Stuff release processes, you're welcome to maintain
>> your own projects and release them at your own schedule.
>
>
> Your way or the highway ?
> I don't consider your reaction very community-friendly. There *are* other
> people contributing to wicket-stuff.
>
>
>>
>>
>> It doesn't make sense to me to go back on a decision that was made,
>> just because 2 folks think it is "better".
>
>
> Until someone opens the discussion, we won't know how many people think it
> is "better" to have separate version numbers.
> But you seem to want to kill the discussion (and you will probably succeed,
> I am giving up already)
>
>
>
>> IMO having a release
>> following Wicket's releases is better than not having a release.
>
>
> true
>
>
>>
>>
>> The problem with Wicket Stuff is not that they follow the Wicket
>> release cycle, it is that nobody gives a damn to cut releases. Jeremy
>> fixed that. If you think you can do better, don't put your project in
>> the Wicket Stuff parent group, but release the software on your own.
>>
>
> Not very constructive.
>
> Regards
> Maarten
>
>
>>
>> Martijn
>>
>>
>> On Wed, Aug 12, 2009 at 3:36 PM, Reinhard
>> Nägele<re...@mgm-tp.com> wrote:
>> > I'd like to second Maartens point. Identical releases to Wicket itself
>> would
>> > mean that it always depends on Wicket. Independent releases would not be
>> > possible. Bugs could not be fixed and new features could not be added
>> > without a new Wicket release. This doesn't really make sense to me.
>> >
>> > Reinhard
>> >
>> >
>> > Jeremy Thomerson schrieb:
>> >>>>
>> >>>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version
>> is
>> >>>> compatible. There is no 1.4.0 version of wicketstuff core (yet?).
>> Should
>> >>>> I
>> >>>> use 1.4-rc8-SNAPSHOT?
>> >>>>
>> >>
>> >> It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental
>> >> relic of after I built rc8
>> >>
>> >>
>> >>>
>> >>> Side note: I don't see the version of wicket-stuff has to match
>> exactly
>> >>> with version of wicket ?
>> >>> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow
>> some
>> >>> bugs are fixed in wicketstuff-core, then we can't release these
>> bug-fixes
>> >>> until wicket 1.4.1 is out ?
>> >>>
>> >>> IMO, wicket is just a dependency of wicketstuff-code (as defoined in
>> the
>> >>> pom) and both projects should use their own unrelated version numbers.
>> >>>
>> >>> wdyt ?
>> >>>
>> >>
>> >> When I setup wicketstuff-core, I proposed that we structure it to have
>> >> identical releases to Wicket. The community agreed. I still think
>> >> this should be the case.
>> >> --
>> >> Jeremy Thomerson
>> >> http://www.wickettraining.com
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> >> For additional commands, e-mail: users-help@wicket.apache.org
>> >>
>> >>
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> > For additional commands, e-mail: users-help@wicket.apache.org
>> >
>> >
>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.4 increases type safety for web applications
>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by Maarten Bosteels <mb...@gmail.com>.
Martijn,
First off: I do appreciate the time and work that Jeremy spends on
wicketstuff
On Wed, Aug 12, 2009 at 4:05 PM, Martijn Dashorst <
martijn.dashorst@gmail.com> wrote:
> Given the lackluster release history of Wicket Stuff, I'd suggest
> going with whatever the only person able *AND* willing to cut releases
> wants. In this case, that is Jeremy. If you don't want to follow the
> general Wicket Stuff release processes, you're welcome to maintain
> your own projects and release them at your own schedule.
Your way or the highway ?
I don't consider your reaction very community-friendly. There *are* other
people contributing to wicket-stuff.
>
>
> It doesn't make sense to me to go back on a decision that was made,
> just because 2 folks think it is "better".
Until someone opens the discussion, we won't know how many people think it
is "better" to have separate version numbers.
But you seem to want to kill the discussion (and you will probably succeed,
I am giving up already)
> IMO having a release
> following Wicket's releases is better than not having a release.
true
>
>
> The problem with Wicket Stuff is not that they follow the Wicket
> release cycle, it is that nobody gives a damn to cut releases. Jeremy
> fixed that. If you think you can do better, don't put your project in
> the Wicket Stuff parent group, but release the software on your own.
>
Not very constructive.
Regards
Maarten
>
> Martijn
>
>
> On Wed, Aug 12, 2009 at 3:36 PM, Reinhard
> Nägele<re...@mgm-tp.com> wrote:
> > I'd like to second Maartens point. Identical releases to Wicket itself
> would
> > mean that it always depends on Wicket. Independent releases would not be
> > possible. Bugs could not be fixed and new features could not be added
> > without a new Wicket release. This doesn't really make sense to me.
> >
> > Reinhard
> >
> >
> > Jeremy Thomerson schrieb:
> >>>>
> >>>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version
> is
> >>>> compatible. There is no 1.4.0 version of wicketstuff core (yet?).
> Should
> >>>> I
> >>>> use 1.4-rc8-SNAPSHOT?
> >>>>
> >>
> >> It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental
> >> relic of after I built rc8
> >>
> >>
> >>>
> >>> Side note: I don't see the version of wicket-stuff has to match
> exactly
> >>> with version of wicket ?
> >>> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow
> some
> >>> bugs are fixed in wicketstuff-core, then we can't release these
> bug-fixes
> >>> until wicket 1.4.1 is out ?
> >>>
> >>> IMO, wicket is just a dependency of wicketstuff-code (as defoined in
> the
> >>> pom) and both projects should use their own unrelated version numbers.
> >>>
> >>> wdyt ?
> >>>
> >>
> >> When I setup wicketstuff-core, I proposed that we structure it to have
> >> identical releases to Wicket. The community agreed. I still think
> >> this should be the case.
> >> --
> >> Jeremy Thomerson
> >> http://www.wickettraining.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.4 increases type safety for web applications
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Wicketstuff releases?
Posted by Martijn Dashorst <ma...@gmail.com>.
Given the lackluster release history of Wicket Stuff, I'd suggest
going with whatever the only person able *AND* willing to cut releases
wants. In this case, that is Jeremy. If you don't want to follow the
general Wicket Stuff release processes, you're welcome to maintain
your own projects and release them at your own schedule.
It doesn't make sense to me to go back on a decision that was made,
just because 2 folks think it is "better". IMO having a release
following Wicket's releases is better than not having a release.
The problem with Wicket Stuff is not that they follow the Wicket
release cycle, it is that nobody gives a damn to cut releases. Jeremy
fixed that. If you think you can do better, don't put your project in
the Wicket Stuff parent group, but release the software on your own.
Martijn
On Wed, Aug 12, 2009 at 3:36 PM, Reinhard
Nägele<re...@mgm-tp.com> wrote:
> I'd like to second Maartens point. Identical releases to Wicket itself would
> mean that it always depends on Wicket. Independent releases would not be
> possible. Bugs could not be fixed and new features could not be added
> without a new Wicket release. This doesn't really make sense to me.
>
> Reinhard
>
>
> Jeremy Thomerson schrieb:
>>>>
>>>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
>>>> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should
>>>> I
>>>> use 1.4-rc8-SNAPSHOT?
>>>>
>>
>> It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental
>> relic of after I built rc8
>>
>>
>>>
>>> Side note: I don't see the version of wicket-stuff has to match exactly
>>> with version of wicket ?
>>> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
>>> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
>>> until wicket 1.4.1 is out ?
>>>
>>> IMO, wicket is just a dependency of wicketstuff-code (as defoined in the
>>> pom) and both projects should use their own unrelated version numbers.
>>>
>>> wdyt ?
>>>
>>
>> When I setup wicketstuff-core, I proposed that we structure it to have
>> identical releases to Wicket. The community agreed. I still think
>> this should be the case.
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by nino martinez wael <ni...@gmail.com>.
And thats suffix not suffic..
2009/8/12 nino martinez wael <ni...@gmail.com>:
> could'nt we just suffic the version with a specific wicketstuff
> release number.. So for wicket 1.4.rc8 it would be
> 1.4.rc8.wicketstuffreleasenumber = 1.4.rc8.44 ? Etc.. That way the 3
> first refer to the wicket number and the last to the wicketstuff one
> or will it bring too much confusion?
>
> 2009/8/12 Reinhard Nägele <re...@mgm-tp.com>:
>> I'd like to second Maartens point. Identical releases to Wicket itself would
>> mean that it always depends on Wicket. Independent releases would not be
>> possible. Bugs could not be fixed and new features could not be added
>> without a new Wicket release. This doesn't really make sense to me.
>>
>> Reinhard
>>
>>
>> Jeremy Thomerson schrieb:
>>>>>
>>>>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
>>>>> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should
>>>>> I
>>>>> use 1.4-rc8-SNAPSHOT?
>>>>>
>>>
>>> It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental
>>> relic of after I built rc8
>>>
>>>
>>>>
>>>> Side note: I don't see the version of wicket-stuff has to match exactly
>>>> with version of wicket ?
>>>> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
>>>> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
>>>> until wicket 1.4.1 is out ?
>>>>
>>>> IMO, wicket is just a dependency of wicketstuff-code (as defoined in the
>>>> pom) and both projects should use their own unrelated version numbers.
>>>>
>>>> wdyt ?
>>>>
>>>
>>> When I setup wicketstuff-core, I proposed that we structure it to have
>>> identical releases to Wicket. The community agreed. I still think
>>> this should be the case.
>>> --
>>> Jeremy Thomerson
>>> http://www.wickettraining.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by nino martinez wael <ni...@gmail.com>.
could'nt we just suffic the version with a specific wicketstuff
release number.. So for wicket 1.4.rc8 it would be
1.4.rc8.wicketstuffreleasenumber = 1.4.rc8.44 ? Etc.. That way the 3
first refer to the wicket number and the last to the wicketstuff one
or will it bring too much confusion?
2009/8/12 Reinhard Nägele <re...@mgm-tp.com>:
> I'd like to second Maartens point. Identical releases to Wicket itself would
> mean that it always depends on Wicket. Independent releases would not be
> possible. Bugs could not be fixed and new features could not be added
> without a new Wicket release. This doesn't really make sense to me.
>
> Reinhard
>
>
> Jeremy Thomerson schrieb:
>>>>
>>>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
>>>> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should
>>>> I
>>>> use 1.4-rc8-SNAPSHOT?
>>>>
>>
>> It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental
>> relic of after I built rc8
>>
>>
>>>
>>> Side note: I don't see the version of wicket-stuff has to match exactly
>>> with version of wicket ?
>>> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
>>> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
>>> until wicket 1.4.1 is out ?
>>>
>>> IMO, wicket is just a dependency of wicketstuff-code (as defoined in the
>>> pom) and both projects should use their own unrelated version numbers.
>>>
>>> wdyt ?
>>>
>>
>> When I setup wicketstuff-core, I proposed that we structure it to have
>> identical releases to Wicket. The community agreed. I still think
>> this should be the case.
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by Reinhard Nägele <re...@mgm-tp.com>.
I'd like to second Maartens point. Identical releases to Wicket itself
would mean that it always depends on Wicket. Independent releases would
not be possible. Bugs could not be fixed and new features could not be
added without a new Wicket release. This doesn't really make sense to me.
Reinhard
Jeremy Thomerson schrieb:
>>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
>>> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should I
>>> use 1.4-rc8-SNAPSHOT?
>>>
>
> It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental
> relic of after I built rc8
>
>
>> Side note: I don't see the version of wicket-stuff has to match exactly
>> with version of wicket ?
>> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
>> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
>> until wicket 1.4.1 is out ?
>>
>> IMO, wicket is just a dependency of wicketstuff-code (as defoined in the
>> pom) and both projects should use their own unrelated version numbers.
>>
>> wdyt ?
>>
>
> When I setup wicketstuff-core, I proposed that we structure it to have
> identical releases to Wicket. The community agreed. I still think
> this should be the case.
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by Ryan McKinley <ry...@gmail.com>.
On Aug 12, 2009, at 9:11 AM, Jeremy Thomerson wrote:
>>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core
>>> version is
>>> compatible. There is no 1.4.0 version of wicketstuff core (yet?).
>>> Should I
>>> use 1.4-rc8-SNAPSHOT?
>
> It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental
> relic of after I built rc8
>
>> Side note: I don't see the version of wicket-stuff has to match
>> exactly
>> with version of wicket ?
>> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow
>> some
>> bugs are fixed in wicketstuff-core, then we can't release these bug-
>> fixes
>> until wicket 1.4.1 is out ?
>>
>> IMO, wicket is just a dependency of wicketstuff-code (as defoined
>> in the
>> pom) and both projects should use their own unrelated version
>> numbers.
>>
>> wdyt ?
>
> When I setup wicketstuff-core, I proposed that we structure it to have
> identical releases to Wicket. The community agreed. I still think
> this should be the case.
I agree. I also like the idea of monthly wicketstuff "release" builds.
I'm not sure this would work, but perhaps we could have each month
release everything in wicketstuff-core with the wicket dependency
pointed to the latest stable wicket release. If any project fails to
build with the latest stable release (say it depends on 1.5, not
1.4.0) that is fine, but it will not get a monthly release.
just brainstorming...
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by Jeremy Thomerson <je...@wickettraining.com>.
>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
>> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should I
>> use 1.4-rc8-SNAPSHOT?
It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental
relic of after I built rc8
> Side note: I don't see the version of wicket-stuff has to match exactly
> with version of wicket ?
> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
> until wicket 1.4.1 is out ?
>
> IMO, wicket is just a dependency of wicketstuff-code (as defoined in the
> pom) and both projects should use their own unrelated version numbers.
>
> wdyt ?
When I setup wicketstuff-core, I proposed that we structure it to have
identical releases to Wicket. The community agreed. I still think
this should be the case.
--
Jeremy Thomerson
http://www.wickettraining.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by Erik van Oosten <e....@grons.nl>.
Maarten,
> AFAIK wicketstuff-core trunk is compatible with wicket 1.4.0
Yes, I know. But my client is not really happy about using trunk/snapshots
in a production system. And frankly, neither am I. I love snapshot
releases, but if I can prevent the extra steps needed to use them in
production I would.
> Side note: I don't see the version of wicket-stuff has to match exactly
> with version of wicket ?
> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
> until wicket 1.4.1 is out ?
I agree. Its just that right now there is no release at all.
As soon as there are more releases of the wicketstuff-core projects and/or
wicket, it makes sense to start a compatibility matrix.
BTW, I don't really care if wicketstuff-core is completely 100% stable, it
will never be. Promoting every first snapshot of the month to a release is
good enough for me.
Regards,
Erik.
On Wed, 12 Aug 2009 10:24:07 +0200, Maarten Bosteels
<mb...@gmail.com> wrote:
> Hello,
>
> On Wed, Aug 12, 2009 at 10:16 AM, Erik van Oosten
> <e....@grons.nl>wrote:
>
>>
>> Hello,
>>
>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
>> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should
>> I
>> use 1.4-rc8-SNAPSHOT?
>
>
> AFAIK wicketstuff-core trunk is compatible with wicket 1.4.0
>
> Side note: I don't see the version of wicket-stuff has to match exactly
> with version of wicket ?
> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
> until wicket 1.4.1 is out ?
>
> IMO, wicket is just a dependency of wicketstuff-code (as defoined in the
> pom) and both projects should use their own unrelated version numbers.
>
> wdyt ?
>
> Maarten
>
>
>>
>>
>> I guess http://sourceforge.net/projects/wicket-stuff/files/ is no longer
>> in
>> use.
>>
>> Regards,
>> Erik.
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by Maarten Bosteels <mb...@gmail.com>.
Hello,
On Wed, Aug 12, 2009 at 10:16 AM, Erik van Oosten <e....@grons.nl>wrote:
>
> Hello,
>
> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should I
> use 1.4-rc8-SNAPSHOT?
AFAIK wicketstuff-core trunk is compatible with wicket 1.4.0
Side note: I don't see the version of wicket-stuff has to match exactly
with version of wicket ?
Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
until wicket 1.4.1 is out ?
IMO, wicket is just a dependency of wicketstuff-code (as defoined in the
pom) and both projects should use their own unrelated version numbers.
wdyt ?
Maarten
>
>
> I guess http://sourceforge.net/projects/wicket-stuff/files/ is no longer
> in
> use.
>
> Regards,
> Erik.
>
>
> --
> Erik van Oosten
> http://day-to-day-stuff.blogspot.com/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Wicketstuff releases?
Posted by Johannes Schneider <ma...@cedarsoft.com>.
By the way:
Wicketstuff contains an old repository definition that should be removed
(in input-events).
Thanks,
Johannes
Johannes Schneider wrote:
> Any news here? I want to use input-events which has not been released
> yet. Any timeline for that module?
>
>
> Thanks,
>
> Johannes
>
> Erik van Oosten wrote:
>> Hello,
>>
>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
>> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should I
>> use 1.4-rc8-SNAPSHOT?
>>
>> I guess http://sourceforge.net/projects/wicket-stuff/files/ is no longer in
>> use.
>>
>> Regards,
>> Erik.
>>
>>
>> --
>> Erik van Oosten
>> http://day-to-day-stuff.blogspot.com/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicketstuff releases?
Posted by Johannes Schneider <ma...@cedarsoft.com>.
Any news here? I want to use input-events which has not been released
yet. Any timeline for that module?
Thanks,
Johannes
Erik van Oosten wrote:
> Hello,
>
> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should I
> use 1.4-rc8-SNAPSHOT?
>
> I guess http://sourceforge.net/projects/wicket-stuff/files/ is no longer in
> use.
>
> Regards,
> Erik.
>
>
> --
> Erik van Oosten
> http://day-to-day-stuff.blogspot.com/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org