On Wed, Jun 29, 2011 at 2:06 PM, Rickard Öberg <[email protected]> wrote:
> and then just add LongService.class and StringService.class to the assembly.
> I.e. in the assembly there's no generics, but the actual service itself may
> be.
We should perhaps consider it even further than that, in which case we
might end up with more extensive need for generics support possibly
reaching to assembly as well, in which case we might end up needing
the TypeLiteral approach (instead of only .class). I guess some
usecases should be constructed and discussed.
> *If* we do the suggested change for EntityFinder into being Finder<T> then
> this is needed by internal lookups anyway, so it was good that you brought
> it up.
I have still not consumed that email...
> Now the question still remains: when shall I commit all this stuff? I have
> TONS of changes that needs to be pushed to the repo, but I understand we'd
> want to do a 1.3.1 first. Niclas, any ideas on that?
Well, it will be a 1.4 (more functionality).
I suggest that you create a remote branch 2.0 for now. There is a
script in bin/ for that already...
niclas:qi4j-sdk niclas$ cat bin/git-create-remote-branch.sh
#!/bin/sh
# git-create-remote-branch <branch_name>
if [ $# -ne 1 ]; then
echo 1>&2 Usage: $0 branch_name
exit 127
fi
export branch_name=$1
for DIR in core libraries extensions . ; do
cd $DIR
git push origin origin:refs/heads/${branch_name}
git fetch origin
git checkout --track -b ${branch_name} origin/${branch_name}
git pull
cd ..
done
--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java
I live here; http://tinyurl.com/3xugrbk
I work here; http://tinyurl.com/24svnvk
I relax here; http://tinyurl.com/2cgsug
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
