Also deleted the unused branches now!
2018-06-21 17:23 GMT+02:00 Dennis Kieselhorst :
> Great, thank you!
>
> On 2018/06/21 13:59:15, Werner Punz wrote:
> > Just deleted it...>
>
>
Great, thank you!
On 2018/06/21 13:59:15, Werner Punz wrote:
> Just deleted it...>
n 2.3.x to the master branch should we
>>>>> also>
>>>>> > commit to the 2.3.x_ branch? Just want to ensure I'm doing the
>>>>> correct>
>>>>> > deliveries.>
>>>>> >
>>>>> > I assume we just n
for version 2.3.x to the master branch should we
>>>> also>
>>>> > commit to the 2.3.x_ branch? Just want to ensure I'm doing the
>>>> correct>
>>>> > deliveries.>
>>>> >
>>>> > I assume we just need to
gt; I assume we just need to deliver to master for 2.3 changes right now
>>> and>
>>> > then once we start a 2.4 etc we'll catch the 2.3.x branch up to master
>>> and>
>>> > do new forward development in master?>
>>> >
>>> > Thanks,>
&
start a 2.4 etc we'll catch the 2.3.x branch up to master
>>> and>
>>> > do new forward development in master?>
>>> >
>>> > Thanks,>
>>> >
>>> > Paul Nicolucci>
>>> >
>>> >
>>> >
branch up to master
>> and>
>> > do new forward development in master?>
>> >
>> > Thanks,>
>> >
>> > Paul Nicolucci>
>> >
>> >
>> >
>> > From: Dennis Kieselhorst >
>> > To: >
c we'll catch the 2.3.x branch up to master
>> and>
>> > do new forward development in master?>
>> >
>> > Thanks,>
>> >
>> > Paul Nicolucci>
>> >
>> >
>> >
>> > From: Dennis Kieselhorst >
>>
>
> > Thanks,>
> >
> > Paul Nicolucci>
> >
> >
> >
> > From: Dennis Kieselhorst >
> > To: >
> > Date: 05/23/2018 06:20 AM>
> > Subject: Re: Migrate all MyFaces projects to Git>
> >
> >
> >
> > >
2.4 etc we'll catch the 2.3.x branch up to master
and>
> do new forward development in master?>
>
> Thanks,>
>
> Paul Nicolucci>
>
>
>
> From: Dennis Kieselhorst >
> To: >
> Date: 05/23/2018 06:20 AM>
> Subject: Re: Migrate all MyFaces
is
> Kieselhorst ---05/23/2018 06:20:13 AM---> AFAICS you merged the 2.3.x into
> master, right? Shoudln't we remove the > 2.3.x branch then?
>
> From: Dennis Kieselhorst
> To:
> Date: 05/23/2018 06:20 AM
> Subject: Re: Migrate all MyFaces projects to Git
> ---
2.3.x branch then?
>
> From: Dennis Kieselhorst
> To:
> Date: 05/23/2018 06:20 AM
> Subject: Re: Migrate all MyFaces projects to Git
> --
>
>
>
> > AFAICS you merged the 2.3.x into master, right? Shoudln't we remove the
> > 2.3
right now and
then once we start a 2.4 etc we'll catch the 2.3.x branch up to master and
do new forward development in master?
Thanks,
Paul Nicolucci
From: Dennis Kieselhorst
To:
Date: 05/23/2018 06:20 AM
Subject: Re: Migrate all MyFaces projects to Git
> AFAICS you mer
> AFAICS you merged the 2.3.x into master, right? Shoudln't we remove the
> 2.3.x branch then?
You are right. I was waiting for other opinions regarding 2.4.x in master. For
now I've removed the 2.3.x branch.
Regards
Dennis
@dennis
AFAICS you merged the 2.3.x into master, right? Shoudln't we remove the
2.3.x branch then?
2018-05-14 20:48 GMT+02:00 Dennis Kieselhorst :
> So the git migration is finished from INFRA point of view. All active
> projects from SVN have been moved to git and all previous
So the git migration is finished from INFRA point of view. All active projects
from SVN have been moved to git and all previous mirrored repos have also been
transfered (except portlet-bridge which was never setup properly and therefore
removed).
In total we have now 11 repos:
Build-tools are now also finished, please use
https://gitbox.apache.org/repos/asf/myfaces-build-tools.git or
https://github.com/apache/myfaces-build-tools from now (default branch is
currently wrong on GitHub, needs to be fixed by INFRA).
The site needs an update. Several places still mention
> > WDYT about deleting some unused branches?
> > IMO we can remove everything, we just need the normal versions like 2.2.x,
> > 1.1.x, ...
> >
> > 2.1.x-client-window, 2.1.x-copy, 2.0.8_windowid_prototype, ... can be
> > removerd.
I agree, feel free to remove them. I just took over what we had
Thanks Dennis. I cloned again today. Its version 2.3.2-SNAPSHOT now. I heard
jsf 2.3 or 2.4 is last. Since work goes on for 2.3.2 its good to be at
2.3.2-SNAPSHOT.
On Wednesday, May 9, 2018, 2:02:50 PM GMT+5:30, Thomas Andraschko
wrote:
About the 2.3.x
About the 2.3.x branch:
IMO we could also set the master to 2.4.x and leave the 2.3.x branch as it
is.
Or should we until the work on JSF.next starts?
2018-05-09 10:27 GMT+02:00 Thomas Andraschko :
> Thanks Dennis!
>
> WDYT about deleting some unused branches?
> IMO
Thanks Dennis!
WDYT about deleting some unused branches?
IMO we can remove everything, we just need the normal versions like 2.2.x,
1.1.x, ...
2.1.x-client-window, 2.1.x-copy, 2.0.8_windowid_prototype, ... can be
removerd.
2018-05-08 22:12 GMT+02:00 Dennis Kieselhorst :
>
To avoid further confusion I've just done the merge from 2.3.x to master.
Please have a look, if everything is fine for you. After that we can delete the
2.3.x branch.
Cheers
Dennis
You need to switch to 2.3.x branch. Master still points to 2.2.x because this
was trunk before the migration.
It is 2.2.13-SNAPSHOT
On Tuesday, May 8, 2018, 10:07:29 PM GMT+5:30, Dora Rajappan
wrote:
I could just clone it. Thank you. Hope its 2.3.1.On Tuesday, May 8, 2018,
9:50:58 PM GMT+5:30, Dennis Kieselhorst wrote:
So the migration
I could just clone it. Thank you. Hope its 2.3.1.On Tuesday, May 8, 2018,
9:50:58 PM GMT+5:30, Dennis Kieselhorst wrote:
So the migration of MyFaces Core is done. Please use
https://gitbox.apache.org/repos/asf/myfaces.git or
https://github.com/apache/myfaces from
So the migration of MyFaces Core is done. Please use
https://gitbox.apache.org/repos/asf/myfaces.git or
https://github.com/apache/myfaces from now.
Any volunteer who merges 2.3.x to master (former 2.2.x trunk)? I think it makes
sense to switch now.
I'll continue with build-tools, it's more
As you might have read in the INFRA issue we are close to migrate the core repo
so please do not commit until further notice. This simplifies the migration
process. I already have a local git repo, just waiting for INFRA to cleanup old
mirrors.
test has been moved to https://gitbox.apache.org/repos/asf/myfaces-test.git and
https://github.com/apache/myfaces-test
myfaces-master-pom has been moved to
https://gitbox.apache.org/repos/asf/myfaces-master-pom.git and
https://github.com/apache/myfaces-master-pom
I was unable to clone myfaces-core from svn:
Checksum mismatch:
> > I tried to convert the existing svn repo to git, but unfortunately there
> > are historical svn authors like royalts, dave, o_rossmueller, How
> > to map them? Are there corresponding Apache committer names or should I use
> > dev-n...@apache.org for them?
I found out that those
+1 for dev-null
2018-04-26 14:47 GMT+02:00 Dennis Kieselhorst :
> > I've opened an INFRA issue to get the repos ready:
> https://issues.apache.org/jira/browse/INFRA-16402
>
> Got feedback from INFRA, plan is to update existing myfaces repo first and
> then migrate it to Gitbox.
> I've opened an INFRA issue to get the repos ready:
> https://issues.apache.org/jira/browse/INFRA-16402
Got feedback from INFRA, plan is to update existing myfaces repo first and then
migrate it to Gitbox.
I tried to convert the existing svn repo to git, but unfortunately there are
I've opened an INFRA issue to get the repos ready:
https://issues.apache.org/jira/browse/INFRA-16402
Yep thats true.
It was just an idea to minimize required projects.
2018-04-12 10:50 GMT+02:00 Udo Schnurpfeil :
> When you only have the examples folder, it can't work.
>
> About MyFaces-Core: you will need a copy for each version of MyFaces
> 2.0, 2.1, 2.2., 2.3.
>
>
When you only have the examples folder, it can't work.
About MyFaces-Core: you will need a copy for each version of MyFaces
2.0, 2.1, 2.2., 2.3.
Nevertheless, I see no reason to restructure the build process only for
a git migration.
Regards,
Udo
Am 12.04.18 um 10:33 schrieb Thomas
It works fine for my personal projects.
/myfaces-tobago/pom.xml
/myfaces-tobago/checkstyle.xml
/myfaces-tobago/examples/pom.xml
/myfaces-tobago/examples/
The examples pom inherit from the root pom and the root pom's checkstyle
plugin has:
checkstyle.xml
No problem to build only the
Sorry for wrong addressing...
The maven-checkstyle-plugin and dependency-check-maven CAN load the
configuration from the file system. But when you do that, it's no longer
possible to build only a sub-module, e.g. an example. That's the reason
why these configuration in a Maven artifact. "It's
Hi Udo, you only sent it to me, now adding dev@myfaces.
What do you mean exactly?
This are just checkstyle files, which can be placed inside tobago itself.
e.g.
/myfaces-tobago/pom.xml
/myfaces-tobago/checkstyle.xml
there is no need to give the checkstyle a own project, it coudl be just a
We should really think about it we need to migrate myfaces-build-tools.
The only active stuff maintained here is the checkstyle, we can be simply
moved the projects.
Extensions is also ExtVal and CODI are not maintained, only
ExtScripting got a small update this year.
2018-04-12 8:47
Yes, everything is working. It's good idea to do the migration.
As far as I can see we need the following repos:
myfaces (for myfaces-core, already exists as old mirror
https://github.com/apache/myfaces)
myfaces-master-pom
myfaces-build-tools
myfaces-extensions
myfaces-test
The other stuff has
Is everything fine now for tobago and trinidad?
+1 for migrating core now as 2.3.0 is out, maybe we have to wait for 2.3.1
we could also do a bit a cleanup and only migrate the active projects
We must also check e.g. the maven plugins and master poms...
E.g. we could remove the checkstyle files
> https://svn.apache.org/repos/asf/myfaces/trinidad-maven/ has not been
> migrated yet, I've requested a new repo for it.
Migration of trinidad-maven is finished:
https://github.com/apache/myfaces-trinidad-maven or
https://gitbox.apache.org/repos/asf?p=myfaces-trinidad-maven.git
I finally managed to migrate trinidad.
Please use https://gitbox.apache.org/repos/asf/myfaces-trinidad.git or
https://github.com/apache/myfaces-trinidad from now on. SVN has been
marked as readonly.
https://svn.apache.org/repos/asf/myfaces/trinidad-maven/ has not been
migrated yet, I've
Big +1 from my side.
Bernd
On Fri, Sep 15, 2017 at 9:23 AM, Dennis Kieselhorst wrote:
> On 2017-09-08 09:49, Dennis Kieselhorst wrote:
> > Trinidad will follow till Sunday.
>
> Short update on Trinidad git migration.
>
> I used the following command:
> git
On 2017-09-08 09:49, Dennis Kieselhorst wrote:
> Trinidad will follow till Sunday.
Short update on Trinidad git migration.
I used the following command:
git svn clone --stdlayout --no-metadata --authors-file=authors.txt
https://svn.apache.org/repos/asf/myfaces/trinidad/
> Finally I have a working setup to migrate the subversion history to git.
> I already started with Tobago yesterday, Trinidad will follow till
Sunday.
>
> The result for Tobago is the following, will send another mail after
> having pushed this to Gitbox:
Tobago is finished:
Finally I have a working setup to migrate the subversion history to git.
I already started with Tobago yesterday, Trinidad will follow till Sunday.
The result for Tobago is the following, will send another mail after
having pushed this to Gitbox:
origin/TOBAGO-1719
origin/lofwyr
The repos are online:
https://gitbox.apache.org/repos/asf/myfaces-tobago.git
https://github.com/apache/myfaces-tobago
https://gitbox.apache.org/repos/asf/myfaces-trinidad.git
https://github.com/apache/myfaces-trinidad
But the myfaces-committers list is a little bit short.
issue created
https://issues.apache.org/jira/browse/INFRA-14883
Regards
Bernd
On Thu, Aug 10, 2017 at 9:45 PM, Dennis Kieselhorst wrote:
> Lazy consensus is fine, please go ahead and file an infra issue. It will
> take some time anyway.
>
Lazy consensus is fine, please go ahead and file an infra issue. It will
take some time anyway.
Proposal migration to git:
We should request migration to gitbox without issues support on github.
I would like to keep Jira as bugtracking tool. We can revisit this later.
We should migrate only active maintained projects.
Candidates are:
Tobago and Trinidad
MyFaces Core
Any objections?
Is a
mojarra download url of github.com is also mirror and it actually goes to
java.net
domain.https://maven.java.net/content/repositories/releases/org/glassfish/javax.faces/2.3.2/
On Friday, July 28, 2017, 2:22:03 PM GMT+5:30, Dora Rajappan
wrote:
Hi ,
Thanks for the
Hi ,
Thanks for the information on Git hub for apache. I found mojarra latest
downloads in github.com and understand the domain is a trusted site from this
discussion. https://github.com/javaserverfaces/mojarra/releases/tag/2.3.2.
Nice to know myfaces projects are going to apache git. I can
And we need a formal vote
Regards
Bernd
On Thu, Jul 27, 2017 at 8:47 PM, Bernd Bohmann wrote:
> We should define a workflow like this:
>
> https://wiki.apache.org/nutch/UsingGit
>
> And we should aware that commiters must enable 2 factor auth on Github and
> add
We should define a workflow like this:
https://wiki.apache.org/nutch/UsingGit
And we should aware that commiters must enable 2 factor auth on Github and
add the github id to the apache profile
see: https://gitbox.apache.org/setup/
On Thu, Jul 27, 2017 at 7:09 PM, Bernd Bohmann
I'm fine with everything with better integration.
Bernd
Am 27.07.2017 17:50 schrieb "Dennis Kieselhorst" :
In the meantime infra launched Gitbox with even better GitHub
integration, so in my view we should use that from the beginning:
http://gitbox.apache.org
In the meantime infra launched Gitbox with even better GitHub
integration, so in my view we should use that from the beginning:
http://gitbox.apache.org
Hello Dora
this is not possible for apache projects
see: https://git-wip-us.apache.org
and
https://www.apache.org/dev/writable-git
but there are readonly mirrors at https://github.com/apache
Regards
Bernd
On Thu, Jul 27, 2017 at 4:10 PM, Dora Rajappan
wrote:
> Is
Is it github.com where you are going to migrate myfaces to?
On Thursday, July 27, 2017, 7:06:06 PM GMT+5:30, Bernd Bohmann
wrote:
for Trinidad as well
On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil wrote:
Hi,
for Tobago I think, we can do
for Trinidad as well
On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil wrote:
> Hi,
>
> for Tobago I think, we can do it now!
>
> Regards,
>
> Udo
>
> Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> > Ok
> >
> > we have some agreement about moving to git.
> > Now we should
Hi,
for Tobago I think, we can do it now!
Regards,
Udo
Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> Ok
>
> we have some agreement about moving to git.
> Now we should define some time line.
> Any suggestions from the active subprojects?
>
> Something like
> 'I would like to move to git
Ok
we have some agreement about moving to git.
Now we should define some time line.
Any suggestions from the active subprojects?
Something like
'I would like to move to git after blah blah release'
'I would like to move now'
'I would like to move in 2 weeks'
or whatever
I can support the
Ah, this may be why it's worked for me -- smaller projects with defined
release cycles.
Anyway, I never meant to imply that git == git flow. We will need some sort
of process, though, and the DeltaSpike one seems like a good place to start.
___
Kito D. Mann | @kito99 | Author, JSF in Action
Web
I prefer working with GIT, and agree with the points already made in this
thread about its benefits. I'm not sure how much pain a meaningful
transition will cause - from that perspective, starting with the components
is a great idea.
+1
Regards,
Bill
On Thu, Apr 20, 2017 at 8:24 AM, Bernd
Thanks Mark
gitflow is not solving any technical problem. It's just more complicated
and it's looks good from a high level perspective.
Regards
Bernd
On Thu, Apr 20, 2017 at 2:02 PM, Mark Struberg wrote:
> gitflow is pure pita ;)
> It basically only works for companies
gitflow is pure pita ;)
It basically only works for companies where you have a single manager who
decides what goes in and what not.
But GIT != gitflow. gitflow has nothing to do with the GIT scm itself, but is
just a fancy name for a development process with an explicit build-branch and a
hi @ all,
just fyi:
[1] works very well for ds since the beginning.
regards,
gerhard
[1] https://deltaspike.apache.org/suggested-git-workflows.html
2017-04-19 14:45 GMT+02:00 Kito Mann :
> Hello Bernd,
>
> I like GitFlow for coordinating with multiple developers.
Hello Bernd,
I like GitFlow for coordinating with multiple developers. However, if
everyone is sending pull requests anyway, it's not quite as useful. It
makes sense when you have multiple developers that are committing to a
"develop" branch and provides guidelines for working with master for new
Until now, nobody could explain me the real technical improvement of
GitFlow.
We are talking about using git and not GitFlow. Git does not require
GitFlow
At Apache we are only using process as much as needed and not as possible!
And my personal advice is:
Start with a model as simple as
+1
Wha's wrong with GitFlow?
___
Kito D. Mann | @kito99 | Author, JSF in Action
Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
Virtua, Inc. | virtua.tech
JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
+1 203-998-0403
* See me speak at the
Hello
I think the changes will be not so complicated. The deltaspike pom looks
nice :-)
If someone talks about git-flow process i'm out.
Regards
Bernd
On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe wrote:
> +1
>
> Change the release process is a pain, but I agree there
+1
Change the release process is a pain, but I agree there are some benefits
moving to git.
But when I see here:
https://github.com/apache/myfaces
It says:
mirrored from git://git.apache.org/myfaces.git
But I have never checked where that file is or how to change it.
Looking in deltaspike,
+1
Couldn't agree more.
Grant Smith - V.P. Information Technology
Marathon Computer Systems, LLC.
On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann
wrote:
> From my side a big
>
> +1
>
> I'm still happy with subversion but for others the collaboration is easier
> and
>From my side a big
+1
I'm still happy with subversion but for others the collaboration is easier
and the project visibility a little bit better.
Regards
Bernd
Am 13.04.2017 09:41 schrieb "Thomas Andraschko" :
> +0
> I usually just work on MF core and there it
+0
I usually just work on MF core and there it doesn't make much difference.
2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :
> Hi,
>
> have you ever thought of migrating to Git? I see more and more Apache
> projects moving. In the past SVN or Git didn't make any difference to me
>
Hi,
have you ever thought of migrating to Git? I see more and more Apache
projects moving. In the past SVN or Git didn't make any difference to me
but now I'm thinking that as an Open Source project you need to be
present on GitHub to get Pull Requests from the community. It's much
more fun
76 matches
Mail list logo