> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "spring-modules-fork" group.
> To post to this group, send email to spring-mo...@googlegroups.com
> To unsubscribe from this group, send email to spring-modules-...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/spring-modules-fork?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
do you have links regarding new modules projects being added?
On 23/01/2010, at 11:24 AM, da...@davidkarlsen.com wrote:
> On Sat, 23 Jan 2010, Antony Stubbs wrote:
>
>> I have sent several emails to spring regarding extensions and have never received a reply. very discouraging. i did all that before starting this fork. So - the whole SE effort seems pretty flawed too.
> Same here (see the forum for spring).
>
> I think it's sensible to stick to the spring extensions where they are already in place (I dropped db40 and another module for those reasons).
>
> Some of the modules have been added quite recently - so there seems to be some development going on over there, although little communication.
>
> --
> David J. M. Karlsen - +47 90 68 22 43
> http://www.davidkarlsen.com
> http://mp3.davidkarlsen.com
> Sent from my bog-standard SMTP client
Wow that's changed a lot since I last saw it, but it still seems modules is quite exclusive - so that's a little reassuring regarding duplicated effort :)
> I emailed spring through their published process to get the "living" modules projects added as spring extensions and received no reply.
Same here.
> do you have links regarding new modules projects being added?
http://www.springsource.org/extensions/list
It's not cronological though, but AFAIK surf and integration adapters are
quite new.
--
> I have sent several emails to spring regarding extensions and have never received a reply. very discouraging. i did all that before starting this fork. So - the whole SE effort seems pretty flawed too.
Same here (see the forum for spring).
I think it's sensible to stick to the spring extensions where they are
already in place (I dropped db40 and another module for those reasons).
Some of the modules have been added quite recently - so there seems to be
some development going on over there, although little communication.
--
is this easy to fix - I have no idea what's causing it - but if you get it
running we could merge it back into the master-master :)
However - David, I haven't been able to merge padlotdlFix's without failing tests and i haven't tried merging tompson's yet. If you guys could check out my versions of their work (tompson-author-fix and padlotdlFix - they just did author re-writes and some commit squashing to track renames properly) and try get your work merging cleanly - or do what david does and merge it for me?
:)
cheers guys!
> --
> You received this message because you are subscribed to the Google Groups "spring-modules-fork" group.
> To post to this group, send email to spring-mo...@googlegroups.com.
> To unsubscribe from this group, send email to spring-modules-...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/spring-modules-fork?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups "spring-modules-fork" group.
> To post to this group, send email to spring-mo...@googlegroups.com.
> To unsubscribe from this group, send email to spring-modules-...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/spring-modules-fork?hl=en.
>
On Jan 29, 9:30 pm, Antony Stubbs <antony.stu...@gmail.com> wrote:
> No worries. Just
> Git fetch origin/pabtoldfix
> Git checkout origin/master - you'll prolly need to make a local branch for
> it.
> Gut merge origin/pabtoldfix
> Mvn clean test
>
> Or something like that ;) and see if it merges clean or fails tests...
>
> Note you can't work on your master anymore - it's been sort of modified. You
> have to work with my master and my pabtoldfix branch.
>
> Regards,
> Antony Stubbs
>
> website: sharca.com
>
> On 30/01/2010, at 9:20 AM, Pablo Saavedra <pablo.a.saave...@gmail.com>
> wrote:
>
> Hey, sorry for the lack of communication. Let me know what tests fail for
> you and I'll see if I can take care. I'm a little overwhelmed with work at
> this moment, so I apologize, but I'll anything I can to help.
>
> Regards.
>
> 2010/1/29 Antony Stubbs <antony.stu...@gmail.com>
>
> > Will do. Have a go with pablotdlFix and tompson-author-fix2 ? :)I couldn't
> > get to merge without failing tests. I have a *hunch* it's dependency version
> > issues.
>
> > On 29/01/2010, at 6:54 AM, davidkarlsen wrote:
>
> > > I've reintegrated dsklyt's fork into my master, and also fixed the
> > > last test that was failing.
> > > You might want to pull this antony - I've tested and it should apply
> > > cleanly to your current master.
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > "spring-modules-fork" group.
> > > To post to this group, send email to
> > spring-mo...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > spring-modules-...@googlegroups.com<spring-modules-fork%2Bunsu...@googlegroups.com>
> > .
> > > For more options, visit this group at
> >http://groups.google.com/group/spring-modules-fork?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "spring-modules-fork" group.
> > To post to this group, send email to spring-mo...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > spring-modules-...@googlegroups.com<spring-modules-fork%2Bunsu...@googlegroups.com>
Regards,
Antony Stubbs
website: sharca.com
On 30/01/2010, at 9:44 AM, Thomas Einwaller
On Jan 29, 10:01 pm, Antony Stubbs <antony.stu...@gmail.com> wrote:
> Yup - try to merge my tompson-author-fix with my master
>
> Regards,
> Antony Stubbs
>
> website: sharca.com
>
> On 30/01/2010, at 9:44 AM, Thomas Einwaller
>
On Sunday, January 31, 2010, <da...@davidkarlsen.com> wrote:
> On Sat, 30 Jan 2010, Antony Stubbs wrote:
>
>
> Hi guys. I've just pushed tompson-author-fix and padlotdlFix which fixes up some of their commits that had problems.
>
> However - David, I haven't been able to merge padlotdlFix's without failing tests and i haven't tried merging tompson's yet. If you guys could check out my versions of their work (tompson-author-fix and padlotdlFix - they just did author re-writes and some commit squashing to track renames properly) and try get your work merging cleanly - or do what david does and merge it for me?
>
> I've fixed pablotdlFix and have named my branch pablotdlFix as well - if you pull that in it should work fine.
>
> --
> David J. M. Karlsen - +47 90 68 22 43
> http://www.davidkarlsen.com
> http://mp3.davidkarlsen.com
> Sent from my bog-standard SMTP client
>
--
___________________________
http://stubbisms.wordpress.com/
I have just pushed "mergeAttempt" which is the combination I'm having trouble with. If you guys who already worked in those areas could take a look at try to get the tests passing - that would be great.
On 1/02/2010, at 12:26 PM, da...@davidkarlsen.com wrote:
> On Mon, 1 Feb 2010, Antony Stubbs wrote:
>
>> It wasn't so much that the branch didn't work, but that when combining
>> it with the new master - it didn't work. Did you try that? The change
>> you made doesn't look like it would fix the problems I saw.
>
> Both JCR and lucene need lucene - but with different versions.
> Let it be dragged in transitively in the jcr module, and declare a dependency for it directly in the lucene module.
>
> I think we should only have a few common libraries controlled at the toplevel, like logging and the spring framework itself.
> To unsubscribe from this group, send email to spring-modules-...@googlegroups.com.
> It wasn't so much that the branch didn't work, but that when combining
> it with the new master - it didn't work. Did you try that? The change
> you made doesn't look like it would fix the problems I saw.
Both JCR and lucene need lucene - but with different versions.
Let it be dragged in transitively in the jcr module, and declare a
dependency for it directly in the lucene module.
I think we should only have a few common libraries controlled at the
toplevel, like logging and the spring framework itself.
--
> Hi guys. I've just pushed tompson-author-fix and padlotdlFix which fixes up some of their commits that had problems.
>
> However - David, I haven't been able to merge padlotdlFix's without failing tests and i haven't tried merging tompson's yet. If you guys could check out my versions of their work (tompson-author-fix and padlotdlFix - they just did author re-writes and some commit squashing to track renames properly) and try get your work merging cleanly - or do what david does and merge it for me?
I've fixed pablotdlFix and have named my branch pablotdlFix as well - if
you pull that in it should work fine.
--