Re: [cross-project-issues-dev] Ready for M5?

[Adrian Sacchi]

I re-enabled scout-rap with the m5 contribution. (Exactly as Markus explained.)

Regards,
Adrian

Von: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] Im Auftrag von Markus 
Knauer
Gesendet: Mittwoch, 4. Februar 2015 00:01
An: Eclipse Cross Project Issues
Betreff: Re: [cross-project-issues-dev] Ready for M5?


scout-rap I think was a recent disable ... perhaps getting ready to re-submit?

I had to temporarily disable their contribution when I updated our RAP 
contributions. That's 'business as usual' and they are informed. I'm sure they 
will enable their configuration as soon as their bits are ready.

Regards, Markus
On 3 Feb 2015 19:47, "David M Williams" 
mailto:david_willi...@us.ibm.com>> wrote:
There are still a number of components or features "disabled" for M5.

birt.b3aggrcon - org.eclipse.simrel.build
mat.b3aggrcon - org.eclipse.simrel.build
mft.b3aggrcon - org.eclipse.simrel.build (2 matches)
scout-rap.b3aggrcon - org.eclipse.simrel.build

The BIRT (and MAT) issue is documented in bug 
458296 .

mft has a few disabled features, which I think have been disabled for along 
time. Should they be removed?

scout-rap I think was a recent disable ... perhaps getting ready to re-submit?

Please post status and outlook, if you are responsible for any of these 
components.

Thanks,

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


smime.p7s
Description: S/MIME cryptographic signature
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] maintenance update site: Unable to satisfy dependency from org.eclipse.platform.feature.group

[Adrian Sacchi]

Hi,

Yes, filtering out the environment works for me.

Thank you, Francisco and Dani, for the hints.
Adrian

Von: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] Im Auftrag von Steve 
Francisco
Gesendet: Dienstag, 2. September 2014 15:19
An: Cross project issues
Betreff: Re: [cross-project-issues-dev] maintenance update site: Unable to 
satisfy dependency from org.eclipse.platform.feature.group

Hi Adrian,
The ppc64le support was recently added for Luna SR1.  Dani mentioned this in a 
recent post to Cross-project-issues:
> If you build against the Platform's repository, or create a mirror of it, and 
> already filter out certain platforms in your build, then you will likely need 
> to also filter out this new platform.
Could you see if that's the case for you?
I have confirmed that the bundles your error message refers to do exist in the 
Luna SR1 RC2 build repository, so I'm hoping your issue is just needing an 
adjustment to your filtering.

-- Steve Francisco

cross-project-issues-dev-boun...@eclipse.org<mailto:cross-project-issues-dev-boun...@eclipse.org>
 wrote on 09/01/2014 09:33:49 AM:

> From: Adrian Sacchi mailto:adrian.sac...@bsiag.com>>
>
> Hi,
>
> For Scout we have a verification build against http://
> download.eclipse.org/releases/maintenance/ where we have a
> dependency to org.eclipse.platform.feature.group.  This dependency
> cannot be resolved because org.eclipse.core.filesystem.linux.ppc64le
> is missing.
>
> This is the error we get:
> Unable to satisfy dependency from org.eclipse.platform.feature.group
> 4.4.0.v20140829-0500 to org.eclipse.core.filesystem.linux.ppc64le
> [1.4.0.v20140808-1353].; Unable to satisfy dependency from
> org.eclipse.e4.rcp.feature.group 1.3.100.v20140828-1642 to
> org.eclipse.equinox.launcher.gtk.linux.ppc64le [1.0.
> 200.v20140409-1208].; Unable to satisfy dependency from
> org.eclipse.e4.rcp.feature.group 1.3.100.v20140828-1642 to
> org.eclipse.swt.gtk.linux.ppc64le [3.103.1.v20140827-1113].; Unable
> to satisfy dependency from org.eclipse.e4.rcp.source.feature.group
> 1.3.100.v20140828-1642 to org.eclipse.swt.gtk.linux.ppc64le.source
> [3.103.1.v20140827-1113].
>
> Could there be a problem with the platform aggregation at the
> maintenance P2 update site?
>
> Regards,
> Adrian


smime.p7s
Description: S/MIME cryptographic signature
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] maintenance update site: Unable to satisfy dependency from org.eclipse.platform.feature.group

[Adrian Sacchi]

Hi,

For Scout we have a verification build against 
http://download.eclipse.org/releases/maintenance/ where we have a dependency to 
org.eclipse.platform.feature.group.  This dependency cannot be resolved because 
org.eclipse.core.filesystem.linux.ppc64le is missing.

This is the error we get:
Unable to satisfy dependency from org.eclipse.platform.feature.group 
4.4.0.v20140829-0500 to org.eclipse.core.filesystem.linux.ppc64le 
[1.4.0.v20140808-1353].; Unable to satisfy dependency from 
org.eclipse.e4.rcp.feature.group 1.3.100.v20140828-1642 to 
org.eclipse.equinox.launcher.gtk.linux.ppc64le [1.0.200.v20140409-1208].; 
Unable to satisfy dependency from org.eclipse.e4.rcp.feature.group 
1.3.100.v20140828-1642 to org.eclipse.swt.gtk.linux.ppc64le 
[3.103.1.v20140827-1113].; Unable to satisfy dependency from 
org.eclipse.e4.rcp.source.feature.group 1.3.100.v20140828-1642 to 
org.eclipse.swt.gtk.linux.ppc64le.source [3.103.1.v20140827-1113].

Could there be a problem with the platform aggregation at the maintenance P2 
update site?

Regards,
Adrian



smime.p7s
Description: S/MIME cryptographic signature
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Status and outlook for Mars M1 and Luna SR1 RC1

[Adrian Sacchi]

We left scout-rap disabled for Mars M1 on purpose. We expect to have it 
included in M2.

Regards
Adrian

Von: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] Im Auftrag von David M 
Williams
Gesendet: Mittwoch, 20. August 2014 21:09
An: cross-project-issues-dev@eclipse.org
Betreff: [cross-project-issues-dev] Status and outlook for Mars M1 and Luna SR1 
RC1

Been a busy few days!

I think we are on the verge of getting some "green" builds again, but wanted to 
be sure to mention some "hacks" I had to make:

For Luna
I disabled
  mylyn-docs-intent.b3aggrcon
  (I also removed "eclipselink" which I hope doesn't surprise them, as they 
were not participants in the Sim. Release! ... definitely need to tighten up 
our process! )

For Mars, more changes. In addition to the above two changes, the following 
contain some repo or feature disabled. The first one in the list (and the last) 
are the only ones I made ...
but thought it'd be good to call attention to the others in case anyone is 
surprised.
I also had to adjust the "feature ranges" of emf.transaction and gmf.runtime. 
emf-transaction I'm pretty sure was a "typo",
but the latter I'm not so sure. I changed (increased) feature ranges so it 
would "match" what was in the repo it was pointing at, but as far as I know it 
might have been pointing at the wrong repo?

soa-bpmn2-modeler.b3aggrcon
emf-emf-rap.b3aggrcon
gef.b3aggrcon
mft.b3aggrcon
scout-rap.b3aggrcon
swtbot.b3aggrcon
mylyn-docs-intent.b3aggrcon


Still a few hours left, if anyone can safely make changes to fix up things to 
be included, or accurate.

The good news is I think the "warm up" RC has been effective in getting Luna 
close to "lined up" ... the next RC's, in a few weeks, will have little time 
for major changes, so I hope this preliminary step avoids problems for those 
that should be "real" release candidates. Also, more good news, I think this is 
the most "M1 participants" we've ever had! ... I am glad everyone is getting a 
good early start on Mars, as it should be.

Thanks!


smime.p7s
Description: S/MIME cryptographic signature
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev