Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [wtp-incubator-dev] Migrate incubator projects to Git?

The JSF Facelets Tools Incubator project will be retired. A separate mail to the dev lists with details will follow. Given this, there is no need to move the JSF Facelets Tools project to Git.
-Raghu

-----Original Message-----
From: Dominik Schadow [mailto:info@xxxxxxxxxxxxxxxxx] 
Sent: Thursday, June 03, 2010 6:48 AM
To: WTP Incubator Dev list
Subject: Re: [wtp-incubator-dev] Migrate incubator projects to Git?

Sorry for the late answer. However I'm perfectly fine with moving to
GIT, so a +1 from me.

Dominik

Am 02.06.10 18:58, schrieb David Carver:
> The Tycho plugin for Maven 3 can generate a P2 repository as well as a
> maven repository.  So you get the best of both worlds.   Maven 3 will
> also allow maven based builds to read p2 repositories and use them just
> as if they were maven repositories.
> 
> Any migration to git for the incubator would need PMC approval.   So far
> I'm seeing +1 votes from the XQuery and VEX projects.    I can +1 for
> RelaxNG as well.    Which I think just leaves the XML Security and any
> JSF projects that may be incubating.
> 
> Dave
> 
> 
> On 06/02/2010 03:35 AM, Igor Lino wrote:
>> ++1
>> I'm happy to hear about the Tycho. I use maven heavily since many
>> years. (I have been personally following the Tycho development since 6
>> months, unfortunately it requires Maven 3 which has not yet a final
>> release and so is not considered stable [company policy]). I could
>> definitively use the infrastructure for build dita-related maven plugins.
>>
>> The question is how to publish released artifacts to the internet? I
>> can imagine some core Vex projects will be reused by other projects
>> building on top of Vex, and having the bundles/artifacts in a maven
>> repository would be a good thing for those external projects.
>>
>> Note that maven has a viral effect. (good or bad, depending how you
>> see it)
>>
>>
>> +1
>> I tried using the eGIT recently and found it very fast but rather
>> complicated (I guess the advantage of having the own repository, means
>> extra overhead dealing with that repository ). Considering not just
>> what is within Eclipse, but the command line tooling, or also the
>> explorer integration tooling (i.e. in Windows).  I think it with get
>> better over time.
>>
>>
>>
>> -------- Original-Nachricht --------
>>   
>>> Datum: Tue, 01 Jun 2010 13:48:26 -0700
>>> Von: David Carver<d_a_carver@xxxxxxxxx>
>>> An: WTP Incubator Dev list<wtp-incubator-dev@xxxxxxxxxxx>
>>> Betreff: [wtp-incubator-dev] Migrate incubator projects to Git?
>>>      
>>   
>>> I'd like to toss out the idea that the WTP Incubator move off of CVS and
>>> over to Git.  The eclipse webmasters put out a general call earlier
>>> asking for interested projects to do the migration.   Since the code in
>>> the incubator is pretty self contained, we could do this on a per
>>> component basis.   It would also give us a place as a group to test out
>>> and figure out any migration issues that can occur and any build
>>> infrastructure changes that may need to occur as well.   The items we
>>> learn here could help benefit the community as a whole.
>>>
>>> There are some risks assummed by this move.  First while the eGit plugin
>>> is improving drastically every day, it still doesn't have all the
>>> feature level support of the CVS client.   So those using git repos
>>> would need to be willing to help out the eGit project and when necessary
>>> move to command line for some items.   I suspect that eGit is going to
>>> get to where it needs to be within the next 3 months.
>>>
>>> There are build issues that will need to be addressed.   I'm planning on
>>> migrating Vex's CI build on Hudson to Maven/Tycho, but keeping existing
>>> functionality in place for the current WTP build.   The speed
>>> improvements I've seen in build times with maven have been pretty
>>> significant compared to other methods I've seen.   PsychoPath the XPath
>>> 2.0 processor went from an average of 20 minutes down to about 2 minutes
>>> for a complete build.   XQuery I've seen similar results, but running
>>> under 50 seconds.
>>>
>>> Anyways, thought I'd toss this out to the incubator committers and get
>>> some feedback.
>>>
>>> Dave
>>>
>>>
>>> _______________________________________________
>>> wtp-incubator-dev mailing list
>>> wtp-incubator-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
>>>      
>> _______________________________________________
>> wtp-incubator-dev mailing list
>> wtp-incubator-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
>>
>>    
> 
> _______________________________________________
> wtp-incubator-dev mailing list
> wtp-incubator-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
> 
_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev


Back to the top