Hi Dan,
I have talked with Lukas Fryc who did the Richfaces migration and they
had more complicated situation and anyway he migrated only Richfaces 4
trunk/branches/tags.
So there is the question how deep we would like to have the history in
new Git repository. I think that it should have at least Seam 2.x SVN
logs.
The issue is that we moved branches at some point in history to new
location and git-svn itself doesn't work it around to get unbreakable
history for branches unless using some git magic like git-filter-branch
and/or join/merge individual cloned Seam SVN branches into the resulted
git repository. I will try to play a little with that, but I don't have
to spend with that a much time.
So if you have any other ideas I am listening ;-).
On Fri, 2011-06-03 at 13:53 -0400, Dan Allen wrote:
Great news indeed!
I second the move to github, perhaps under the organization name
github.com/seam2. That's a surefire way to open up Seam 2 for more
community involvement for those who rely on it heavily and want to see
it keep going. Enough projects have been switched over to git recently
that I'm sure you can grab a script from someone. I would check with
Jay since RichFaces went over most recently.
-Dan
On Fri, Jun 3, 2011 at 08:19, Marek Novotny <mnovotny(a)redhat.com>
wrote:
On Fri, 2011-06-03 at 08:48 -0300, Flavio Costa wrote:
> On Fri, Jun 3, 2011 at 8:05 AM, Marek Novotny
<mnovotny(a)redhat.com>
> wrote:
> Hi Seam devs,
>
> although Seam 2 is now on leaving to the darkness
due new Seam
> 3, I am
> still working on that ;-) to satisfy some old Seam
users who
> wanted
> missing features which is worth to do.
>
> First full Mavenized build of Seam 2, second JSF 2
support.
>
> I have imported transformed Seam 2 sources from my
github
> playground
> into
>
https://svn.jboss.org/repos/seam/branches/community/Seam_2_3/
>
> Marek Schmidt set up hudson/jenkins CI job for that
SVN branch
> at
>
http://ci.jboss.org/jenkins/view/Seam/job/Seam-2.3.X-CI/
>
> Credits go to Martin Genčúr for his great effort on
> transforming Seam 2
> examples into Maven build structure.
>
> This process will be followed by releasing
2.3.0.ALPHA
>
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
> Nice work Marek!
> Glad to hear that Seam 2 users are still getting some love!
>
>
> What are the plans for the 2.3?
> Is the mavenization the only goal (despite of bug fixes, of
course)?
I was a little tightlipped, sorry ;-)
JSF 2, I hope that Arquillian integration should get in too.
>
>
> With tons of JBoss' projects migrating to Git and since
you've already
> made the mavenization in a Git repository, why can't the
development
> simply keep using Git from now on?
Clearly stated I haven't imported the SVN into my github
playgrounf with
SVN history, because it was my private experiment which was a
POC
changed into real transformation.
I will count with move to GITHUB into Seam organization
sometime in near
feature. I just would like to put the base transformation into
the old
Seam SVN repo for keeping SVN history and in parallel cleaning
history
from my github playground, which is not important for keeping
there.
It is also important to say that I tried to keep all things as
they were
in Seam 2.2, but current state has to be polished for final
release. So
check it out and report issues if you find any.
>
>
> Again, nice work!
Thanks!
>
>
> Regards
>
> --
> Flávio Coutinho da Costa
>
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction