[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
Re: [cdt-dev] M4 build for Galileo
|
- From: Vivian Kong <vivkong@xxxxxxxxxx>
- Date: Thu, 18 Dec 2008 11:53:50 -0500
- Delivered-to: cdt-dev@eclipse.org
I was figuring out how the p2 metadata generator works so I wanted to specify where everything exactly were so it's less confusing. I'll use relative links.
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
![Inactive hide details for "Olexiy Buyanskyy" ---12/18/2008 11:22:25 AM---Yes I found that in build.xml <property name="launcher]()
"Olexiy Buyanskyy" ---12/18/2008 11:22:25 AM---Yes I found that in build.xml <property name="launcher" value="/opt/public/download-staging.priv/tools/cdt/releng/org.ecli
![]()
From: | ![]()
"Olexiy Buyanskyy" <olexiyb@xxxxxxxxx> |
![]()
To: | ![]()
"CDT General developers list." <cdt-dev@xxxxxxxxxxx> |
![]()
Date: | ![]()
12/18/2008 11:22 AM |
![]()
Subject: | ![]()
Re: [cdt-dev] M4 build for Galileo |
Yes I found that in build.xml
<property name="launcher" value="/opt/public/download-staging.priv/tools/cdt/releng/org.eclipse.cdt/all/org.eclipse.cdt.releng/tools/org.eclipse.releng.basebuilder/plugins/org.eclipse.equinox.launcher.jar"/>
Why path to org.eclipse.equinox.launcher.jar hard coded if it's available under
tools/org.eclipse.releng.basebuilder/plugins/org.eclipse.equinox.launcher.jar
<java jar="${launcher}" fork="true" timeout="10800000" jvm="/opt/public/common/ibm-java2-ppc-50/bin/java" failonerror="true" maxmemory="768m" error="${zipsdir}/p2errorlog.txt" dir="${buildDirectory}/eclipse" output="${zipsdir}/p2metadata.txt">
Why path to java hardcoded?
On Thu, Dec 18, 2008 at 11:11 AM, Vivian Kong <vivkong@xxxxxxxxxx> wrote:
I started generating p2 metadata for our update site and the master feature got added as one of the features in the p2 repository.
As explained on http://wiki.eclipse.org/WTP/What_we_have_learned_(to_love)_about_P2#Can_a_site_be_both_an_update_manager_site.2C_and_a_P2_repository.3F,
the p2 repo got picked up before the site.xml file (which doesn't include the master feature).
I'll see if there's a way to remove the master feature from the p2 contents.jar/xml file.
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
![Inactive hide details for "Schaefer, Doug" ---12/18/2008 10:24:15 AM---The master feature is our trick to ensure we can build e]()
"Schaefer, Doug" ---12/18/2008 10:24:15 AM---The master feature is our trick to ensure we can build everything at once. It shouldn't be visible to updaters.
The master feature is our trick to ensure we can build everything at once. It shouldn't be visible to updaters.
Doug.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Gvozdev
Sent: Thursday, December 18, 2008 10:06 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] M4 build for Galileo
Upon further examination, it appears that it's "CDT Master Feature" that requires mylyn:
"org.eclipse.cdt.master.feature.group 6.0.0" requires "org.eclipse.cdt.mylyn.feature.group [5.0.0.200812171517]"
If I uncheck "CDT Master Feature", do I miss something important in CDT? If not, why that feature is in the list, what is its purpose?
Thanks,
Andrew
On Thu, Dec 18, 2008 at 9:41 AM, Vivian Kong <vivkong@xxxxxxxxxx> wrote:
I am trying to install CDT 6.0 on eclipse 3.5. I am not interested in mylyn for this particular installation and uncheck Mylyn Bridge feature. Still, Mylyn is required, why is that? Should I raise a bug? Mylyn has been a bit intrusive for me on quite a few occasions.
Thanks,
Andrew
On Wed, Dec 17, 2008 at 4:57 PM, Vivian Kong <vivkong@xxxxxxxxxx> wrote:
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
