Re: [cross-project-issues-dev] Eclipse IDE 2024-06 Project Participation Page

[Jeff Johnston via cross-project-issues-dev]

Hi Wayne,

Linux Tools was missing project release records.  I have updated and added
one for 8.15.0 which is the release for 2024-06.

Thanks,

-- Jeff J.

On Wed, May 22, 2024 at 5:56 PM Wayne Beaton via cross-project-issues-dev <
cross-project-issues-dev@eclipse.org> wrote:

> Greetings folks!
>
> I've assembled the release information for participating projects here
> .
>
> Note that the list of projects reflects our long time practice of only
> including projects whose teams are actively participating in the
> simultaneous release. If you look hard enough, you'll notice that projects
> that have been "sponsored in" by participating projects are absent from the
> list. This is per the requirements. I expect that these requirements will
> change in some future release.
>
> A lot of the releases are quite old, and based on the activity in the
> simrel.build 
> repository,  at least a few projects need to create some release records,
> and some may need to engage in a progress review (I've done my usual thing
> of making by best guess based on the release records in the system).
>
> If your project is contributing a different release than what you see
> here, please ensure that you've created a release record
> , and
> let me know. If your project has not engaged in a progress (or release)
> review  in
> more than one year, please engage with the EMO ASAP to schedule a review.
>
> Be sure to set the New and Noteworthy URL in your release record: it is
> through this relationship that we build the aggregate N&N.
>
> Please make sure that you've made your best effort to engage in the IP Due
> Diligence Process for all third party content before you engage with the
> EMO for review. Bear in mind that you should be engaging in the IP Due
> Diligence Process
>  on an ongoing
> basis and that all releases (regardless of whether or not they correspond
> with a progress or release review) must only contain content that has been
> vetted through the due diligence process. With the Eclipse Dash License
> Tool  and the ability to use it
> to automatically create review requests, it should be *easier than ever*
> before to engage (the README has extensive information on how to engage,
> and does include some pointers for using it with Eclipse Tycho
> -based builds).
> Connect with the EMO if you need assistance.
>
> Here are some things that I've observed:
>
> Eclipse Client Platform has been removed.
>
> The aggrcon files for the following projects are disabled; if any of these
> projects are dropping from the release, please let me know:
>
>- Eclipse Xpand
>- Eclipse BPMN2 Modeler Project
>- Eclipse RCPTT
>
> Let me know what I've missed.
>
> Thanks,
>
> Wayne
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation
>
>
> My working day may not be your working day! Please don’t feel obliged to
> read or reply to this e-mail outside of your normal working hours.
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Problem with Linux Tools 2023-06 M3 contribution

[Jeff Johnston]

Hi Ed,

Thanks for the offer.  Alex was able to get the build going again and I am
just about to push our M3 to org.eclipse.simrel.build - just under the wire
:)

-- Jeff J.

On Wed, May 24, 2023 at 1:47 PM Ed Merks  wrote:

> I’ll hold off until roughly noon here in Europe.  Add me to your Gerrit
> contribution when you get that in place so I can start the process.
> Keeping my fingers crossed.
>
> Sent from my iPhone
>
> On May 24, 2023, at 19:39, Jeff Johnston  wrote:
>
> 
> Hello,
>
> We have an issue with our build process that likely will not be fixed
> until early tomorrow.  If possible, we would have to submit our M3
> milestone then.   Otherwise, to not impede M3 and EPP we can wait until RC1
> to submit our next build as there are no features/fixes added from M2 to
> M3; just dependabot updates.
>
> -- Jeff J.
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Problem with Linux Tools 2023-06 M3 contribution

[Jeff Johnston]

Hello,

We have an issue with our build process that likely will not be fixed until
early tomorrow.  If possible, we would have to submit our M3 milestone
then.   Otherwise, to not impede M3 and EPP we can wait until RC1 to submit
our next build as there are no features/fixes added from M2 to M3; just
dependabot updates.

-- Jeff J.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Should SimRel include updated JustJ

[Jeff Johnston]

A user recently opened an issue against JDT UI because they were trying to
update their 2022-06 Eclipse IDE for Java Developers and it fails because
the current JustJ they had: 15.0.1 is not sufficient to update components
which now require Java 17.

While they can manually add the needed JustJ updates site would it not make
sense to make a JustJ update available automatically for such end-users at
least in the case where Eclipse increases minimum JVM requirements?

-- Jeff J.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] 2022-09 Participation

[Jeff Johnston]

Hi Wayne,

Linux Tools should be 8.8.0.  I have created a release record.

-- Jeff J.

On Tue, Aug 30, 2022 at 11:27 PM Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:

> Greetings folks!
>
> I've assembled my first pass at the Eclipse IDE 2022-09 participation page
> .
>
> Please have a look to ensure that I've captured the release version of
> your project correctly. If you're contributing a new release, please be
> sure to create the release record.
>
> You may notice that Maven Integration for Web Tools Platform is dropped
> from the project list. That project was terminated and its resources were
> merged into Maven Integration.
>
> Some anomalies that I've noticed:
>
>- The Eclipse Platform release record has not been created yet;
>- Eclipse ACTF's aggrcon is disabled;
>- Eclipse PDT's aggrcon is disabled; and
>- Eclipse DLTK's aggrcon is disabled.
>
> Can a committer from Eclipse Platform please create the release record?
>
> Regarding the disabled contributions... Can a representative from the
> corresponding project committers please let us know if you are engaged
> working on getting these contributions back into an enabled state?
>
> If your project is contributing a new major or minor release to 2022-09
> and you haven't engaged in a release or progress review in the year leading
> up to your release date, please engage with the EMO ASAP.
>
> Remember that, regardless of whether or not a review is required, any
> intellectual property included in any release must be fully vetted. If you
> have not already done so, I recommend that you check out the Eclipse Dash
> License Tool to identify any gaps in the vetting of your third-party
> dependencies; look especially at the Automatic IP Team Review Requests
> 
> feature.
>
> Thanks,
>
> Wayne
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation
>
>
> My working day may not be your working day! Please don’t feel obliged to
> read or reply to this e-mail outside of your normal working hours.
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] 2022-06 Participation Page

[Jeff Johnston]

I have created the release record for Linux Tools 8.7.0.  Thanks for the
reminder.

-- Jeff J.

On Wed, Jun 8, 2022 at 3:32 PM Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:

> Greetings Simultaneous Release Committers!
>
> It's that time of quarter (actually I think that I'm at least several
> weeks late this time), where we have a quick look at the list of projects
>  that are participating in
> this iteration of the simultaneous release.
>
> I believe that what I've captured on the 2022-06 release page accurately
> reflects the information in the simrel (aggregator) repository. Let me know
> if I've gotten anything wrong.
>
> I've noted the following:
>
> Eclipse Mylyn is marked as disabled in its aggrcon file, so I've removed
> it from the participating projects list. Eclipse Mylyn Docs still has an
> active aggrcon file, so it remains.
>
> There's been recent work on Eclipse DLTK, but no updates to the aggrcon
> file. Is what we have listed on the page accurate?
>
> Eclipse Linux Tools needs a release record for 8.7. According to our
> records, the project engaged in a successful review in December 2021, so no
> further ceremony is required (that is, no release review or IP Log review
> is required).
>
> The aggrcon file for Eclipse Maven Integration for Web Tools shows a new
> service release with no corresponding release record. The project team can,
> at their discretion, create a release record for the new service release
> (or not). Note that a restructuring review
>  is
> scheduled (to conclude after this release) to merge Eclipse Maven
> Integration for Web Tools into the Eclipse Maven Integration project; the
> result being that the subproject will cease to exist and there will be one
> fewer projects listed in the *next* release, but the corresponding
> functionality will remain.
>
> Is it time for Eclipse LSP4e, Eclipse LSP4j, Eclipse TM4E and Eclipse Wild
> Web Developer to graduate?
>
> While I have your attention... Please take note that a revision to the
> Eclipse Foundation's IP Policy is being delivered to the Board of Directors
> for their approval. Our expectation is that the revision will be approved
> and go into effect at the end of July 2022. There will be corresponding
> changes to the IP Due Diligence Process. We've *started* capturing the
> related work (which includes the retirement of IPZilla) in a Eclipse Help
> Desk Issue .
> There's a presentation attached to the issue that describes the IP Policy
> changes. Please post any questions you have on that issue or one of the
> issues that it references.
>
> Thanks,
>
> Wayne
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation
>
>
> My working day may not be your working day! Please don’t feel obliged to
> read or reply to this e-mail outside of your normal working hours.
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Linux Tools build cannot write to standard output location

[Jeff Johnston]

Hello,

Something has changed in the build infrastructure since last week and our
Linux Tools master build pipeline is failing when it tries to write to the
standard updates-nightly output directory we use.

Is there something we can do or is this a new infrastructure issue?  I
didn't see any posting about anything other than the removal of git
protocol which I had fixed last week and the jar signer plug-in version
which we exceed.

-- Jeff J.

[Pipeline] // stage[Pipeline] stage[Pipeline] { (Deploy)[Pipeline]
sshagent[ssh-agent] Using credentials genie.linuxtools
(ssh://genie.linuxto...@projects-storage.eclipse.org)
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent]   Exec ssh-agent (binary ssh-agent on a remote machine)
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-JKaxH65G7Ffd/agent.1134
SSH_AGENT_PID=1136
Running ssh-add (command line suppressed)
Identity added:
/home/jenkins/agent/workspace/linuxtools-master@tmp/private_key_13458881067364320014.key
(/home/jenkins/agent/workspace/linuxtools-master@tmp/private_key_13458881067364320014.key)
[ssh-agent] Started.[Pipeline] {[Pipeline] sh+ ssh
genie.linuxto...@projects-storage.eclipse.org rm -rf
'/home/data/httpd/download.eclipse.org/linuxtools/updates-nightly/*'
Permission denied, please try again.
Permission denied, please try
again.genie.linuxto...@projects-storage.eclipse.org: Permission denied
(publickey,password).
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Problem with repo.eclipse.org and simrel gerrit verification

[Jeff Johnston]

I tried retriggering yesterday afternoon multiple times until about dinner
time.  It appears the problem was known so no issues.

-- Jeff J.

On Tue, Jun 8, 2021 at 8:23 PM Jonah Graham  wrote:

> Is this a fresh error? Repo.eclipse was down most of the afternoon
> https://www.eclipsestatus.io/incidents/9zv3vwwhn0rg
>
> Jonah
>
> On Tue., Jun. 8, 2021, 20:09 Jeff Johnston,  wrote:
>
>> I am seeing the following error trying to to get gerrit to verify for the 
>> Linux Tools RC2 simrel
>>
>> contribution.  Can somebody take a look?  I have ignored the failure and 
>> updated our contribution regardless as local
>>
>> validation works fine.
>>
>>
>> [ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its 
>> dependencies could not be resolved: Failed to read artifact descriptor for 
>> org.apache.maven.plugins:maven-clean-plugin:jar:2.5: Could not transfer 
>> artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.5 from/to 
>> eclipse.maven.central.mirror 
>> (https://repo.eclipse.org/content/repositories/maven_central/): Transfer 
>> failed for 
>> https://repo.eclipse.org/content/repositories/maven_central/org/apache/maven/plugins/maven-clean-plugin/2.5/maven-clean-plugin-2.5.pom
>>  503 Service Unavailable -> [Help 1]
>>
>> -- Jeff J.
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Problem with repo.eclipse.org and simrel gerrit verification

[Jeff Johnston]

I am seeing the following error trying to to get gerrit to verify for
the Linux Tools RC2 simrel

contribution.  Can somebody take a look?  I have ignored the failure
and updated our contribution regardless as local

validation works fine.


[ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one
of its dependencies could not be resolved: Failed to read artifact
descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.5:
Could not transfer artifact
org.apache.maven.plugins:maven-clean-plugin:pom:2.5 from/to
eclipse.maven.central.mirror
(https://repo.eclipse.org/content/repositories/maven_central/):
Transfer failed for
https://repo.eclipse.org/content/repositories/maven_central/org/apache/maven/plugins/maven-clean-plugin/2.5/maven-clean-plugin-2.5.pom
503 Service Unavailable -> [Help 1]

-- Jeff J.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Anyone else having issues pushing to org.eclipse.simrel.build gerrit?

[Jeff Johnston]

I am trying to push the Linux Tools update for 2021-06 RC1 for gerrit
review but I keep getting an error:

To ssh://jjohns...@git.eclipse.org:29418/simrel/org.eclipse.simrel.build.git
 ! [remote rejected] HEAD -> refs/for/master (commit 7d8a3e6: An error
happened while checking commit)
error: failed to push some refs to 'ssh://
jjohns...@git.eclipse.org:29418/simrel/org.eclipse.simrel.build.git'

I added signing to see if that was the issue, but still got the error.  Our
contribution isn't due until tomorrow.

-- Jeff J.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] 2021-06 Participating Projects List

[Jeff Johnston]

Hi Wayne,

Please update Linux Tools to 8.3.0.  I have created a release record.

Thanks,

-- Jeff J.

On Tue, May 18, 2021 at 10:48 AM Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:

> Greetings Folks. It's that time again!
>
> I've created a participation page for the 2021-06 Release
> . On it, I've listed the
> participating projects along with the version that the project is
> contributing to the simultaneous release. Please have a look and let me
> know if anything needs to be updated.
>
> Note that you'll need to create a release record for the release you're
> contributing if you have not already done so (please do so before asking me
> to update your project's participation listing).
>
> Note also that if you have not done so in the last year and you're
> contributing a new major or minor release, you'll need to engage in a release
> review .
>
> Intellectual property must be properly accounted for and tracked at all
> times. The project team must engage in the Eclipse IP Due Diligence
> Process  on an ongoing
> basis. The IP Log review and approval that occurs at the time of either a
> release review or progress review should be regarded as a means of
> confirming that intellectual property is being properly managed and not as
> a trigger to engage in a last minute clean up.
>
> Let me know if you have any questions,
>
> Wayne
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] 2020-12 Release

[Jeff Johnston]

Just to note, I had thought I had created the release record, but I must
not have saved it properly.  I have just created the 8.1.0 release record
and the N&N.

-- Jeff J.

On Thu, Dec 3, 2020 at 11:30 AM Jeff Johnston  wrote:

> Hi Wayne,
>
> I somehow missed this error, but Linux Tools is releasing 8.1.0 for
> 2020-12.  We released 8.0.0 for 2020-09.  We have contributed 8.1.0 to
> simrel for a while now so hopefully it should just be a doc issue.
>
> -- Jeff J.
>
> On Thu, Nov 26, 2020 at 3:45 PM Wayne Beaton <
> wayne.bea...@eclipse-foundation.org> wrote:
>
>> Greetings folks.
>>
>> Thanks for all of your hard work in assembling your contributions to the
>> simultaneous release.
>>
>> I've created the master record ("release page") for the 2020-12
>> simultaneous release <https://projects.eclipse.org/releases/2020-12>.
>> Please have a look at the page and let me know what I've gotten wrong.
>>
>> I've started comparing it to the build aggrcon files and have noticed
>> that a few projects appear to be contributing new releases but have not yet
>> created release records. Please make sure that you've created the
>> release record
>> <https://www.eclipse.org/projects/handbook/#pmi-commands-release> before
>> asking me to update the release page.
>>
>> Selecting the right release record has required some guesswork on my
>> part. I did notice that some of the release records have dates that are
>> later than the simultaneous release date. Please make the value in the
>> release date field for your release record is no later than December
>> 16/2020.
>>
>> There were a few records dated 2020-12-18 that (at least according to the
>> aggrcon files) I believe that I have correctly guessed are participating in
>> the release; there was at least one release dated much later in December
>> that I wasn't sure about and instead opted to pick the previous release as
>> the participating one.
>>
>> If your project's release date is more than one year later than the date
>> of your project's last successful release review, then you must engage in a
>> release review. The EMO will automatically start tracking your release
>> review when you submit your IP Log for review. Note that you only need to
>> submit your IP Log for review or request PMC approval for your release if
>> you are engaging in a release review.
>>
>> Even if your project does not require a release review, you must still
>> take care to ensure that all of the intellectual property included in your
>> release has been property vetted by the IP due diligence process. If you
>> require assistance, please contact the IP Team.
>>
>> Note that the IP Team consults the future release records as input into
>> their prioritization. Please create your release records as early as
>> possible (even if you have to shift the date later) to ensure that we have
>> as much information as possible to assist with prioritization and improve
>> our odds of getting the intellectual property that you care about cleared
>> well in advance of your planned release date.
>>
>> Wayne
>> --
>>
>> Wayne Beaton
>>
>> Director of Open Source Projects | Eclipse Foundation, Inc.
>>
>> Join us at our virtual event: EclipseCon 2020
>> <https://www.eclipsecon.org/2020> - October 20-22
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] 2020-12 Release

[Jeff Johnston]

Hi Wayne,

I somehow missed this error, but Linux Tools is releasing 8.1.0 for
2020-12.  We released 8.0.0 for 2020-09.  We have contributed 8.1.0 to
simrel for a while now so hopefully it should just be a doc issue.

-- Jeff J.

On Thu, Nov 26, 2020 at 3:45 PM Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:

> Greetings folks.
>
> Thanks for all of your hard work in assembling your contributions to the
> simultaneous release.
>
> I've created the master record ("release page") for the 2020-12
> simultaneous release .
> Please have a look at the page and let me know what I've gotten wrong.
>
> I've started comparing it to the build aggrcon files and have noticed that
> a few projects appear to be contributing new releases but have not yet
> created release records. Please make sure that you've created the
> release record
>  before
> asking me to update the release page.
>
> Selecting the right release record has required some guesswork on my part.
> I did notice that some of the release records have dates that are later
> than the simultaneous release date. Please make the value in the release
> date field for your release record is no later than December 16/2020.
>
> There were a few records dated 2020-12-18 that (at least according to the
> aggrcon files) I believe that I have correctly guessed are participating in
> the release; there was at least one release dated much later in December
> that I wasn't sure about and instead opted to pick the previous release as
> the participating one.
>
> If your project's release date is more than one year later than the date
> of your project's last successful release review, then you must engage in a
> release review. The EMO will automatically start tracking your release
> review when you submit your IP Log for review. Note that you only need to
> submit your IP Log for review or request PMC approval for your release if
> you are engaging in a release review.
>
> Even if your project does not require a release review, you must still
> take care to ensure that all of the intellectual property included in your
> release has been property vetted by the IP due diligence process. If you
> require assistance, please contact the IP Team.
>
> Note that the IP Team consults the future release records as input into
> their prioritization. Please create your release records as early as
> possible (even if you have to shift the date later) to ensure that we have
> as much information as possible to assist with prioritization and improve
> our odds of getting the intellectual property that you care about cleared
> well in advance of your planned release date.
>
> Wayne
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation, Inc.
>
> Join us at our virtual event: EclipseCon 2020
>  - October 20-22
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] 2020-06 Release

[Jeff Johnston]

Hi Wayne,

Linux Tools should be 7.7.0 for 2020-06.  I had thought I had created the
release record, but I was mistaken.  Anyway, it is created now.

-- Jeff J.

On Mon, May 25, 2020 at 2:44 PM Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:

> I've updated the records based on feedback.
>
> If you have not done so, please review the list and let me know if
> something isn't right.
>
> https://projects.eclipse.org/releases/2020-06
>
> Wayne
>
> On Wed, May 20, 2020 at 11:59 AM Wayne Beaton <
> wayne.bea...@eclipse-foundation.org> wrote:
>
>> Hey folks!
>>
>> I've created the record for the 2020-06 Simultaneous Release
>> . As usual, I've used the
>> information that I have available to make my best guess at which version
>> you're releasing. If I've got something wrong, please first make sure that
>> you've created a release record with the right date and then let me know to
>> update the corresponding entry on the release page.
>>
>> I noticed that several of the contributions are more than one year old
>> (some of them significantly more). I don't believe that it's necessarily
>> wrong to contribute stable content, but would like to make sure that
>> somebody is periodically testing configurations that include these
>> contributions to mitigate the risk that we ship broken content.
>>
>> Eclipse Tools for Cloud Foundry (2018)
>> Eclipse BIRT (2017)
>> Eclipse Mylyn (2018)
>> Eclipse WindowBuilder (early 2019)
>> Eclipse Xpand (2016)
>> Eclipse Remote Systems Explorer (2018)
>> Eclipse EMFStore (2017)
>> Eclipse BPMN2 Model (2018)
>> Eclipse BPEL Designer (2018)
>> Eclipse ACTF (2017)
>>
>> Wayne
>>
>>
>>
>>
>>
>> --
>>
>> Wayne Beaton
>>
>> Director of Open Source Projects | Eclipse Foundation, Inc.
>>
>> Join us at our virtual event: EclipseCon 2020
>>  - October 20-22
>>
>
>
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation, Inc.
>
> Join us at our virtual event: EclipseCon 2020
>  - October 20-22
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Projects participating in 2019-06

[Jeff Johnston]

Hi Wayne,

The version of Eclipse Linux Tools should be 7.3.0.

Thanks,

-- Jeff J.

On Mon, Jun 3, 2019 at 2:35 PM Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:

> I've updated the project participation
>  list to reflect what I
> believe that I see in the aggregate repository. Please let me know if I've
> gotten something wrong.
>
> ACTF is not in the repository and I don't know why. Their aggrcon file
> looks fine. Have I missed something important?
>
> Note that RC1 is on June 7/2019. If you're pushing new versions/features,
> please update your contribution before this date.
>
> A handful of projects did not signal their intent to participate using the
> described method (nor did they respond to my attempts to use this channel
> to connect). I intend to recommend to the Planning Council that they prune
> out those projects that are clearly not contributing to the process.
>
> Wayne
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation, Inc.
> ___
> 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Linux Tools Participation in 2018.09

[Jeff Johnston]

Linux Tools will be participating in 2018.09 with a point release that has
a +3 offset.

-- Jeff J.
___
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] WTP needs to remove 2 Dali features from simrel & 2 EPP packages (JEE + Reporting) due to missing dependent package com.sun.codemodel

[Jeff Johnston]

Patch has been approved and merged in gerrit.

-- Jeff J.

On Tue, Mar 13, 2018 at 4:36 PM, Nick Boldt  wrote:

> Ran into a bit of a problem in the WTP 3.10.0.M6 build in that there are 2
> dali features - org.eclipse.jpt.dbws.eclipselink.feature and
> org.eclipse.jpt.jaxb.eclipselink.feature - which can't find dependent
> package com.sun.codemodel, so can't be installed.
>
> As such I've removed these 2 features from the simrel site here [1] and
> will need to do the same for EPP, since the build is failing [2].
>
> [1] https://git.eclipse.org/r/#/c/119350/
> [2] https://ci.eclipse.org/packaging/job/photon.epp-
> tycho-build/149/console
>
> Here's a gerrit for that removal [3].
>
> [3] https://git.eclipse.org/r/#/c/119365/ --> https://ci.eclipse.org/
> packaging/job/epp-tycho-build.gerrit/630/
>
> In future, could I get push rights to make changes to the jee and
> reporting packages directly, once the gerrit verification passes?
>
> I hope we can get these re-added for M7, but for now they need to be
> removed.
>
>
> --
>
> Nick Boldt
>
> Senior Software Engineer, RHCSA
>
> Productization Lead :: JBoss Tools & Dev Studio
>
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> 
> TRIED. TESTED. TRUSTED. 
> @ @redhatnews   Red Hat
> 
> 
>
>
> “The Only Thing That Is Constant Is Change” - Heraclitus
>
> ___
> 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 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] Problem with webtools repo for Oxygen.2

[Jeff Johnston]

In doing the latest Linux Tools update for Oxygen_update, I ran into an
issue with a webtools repo which does not exist.  Using the date as a clue,
I changed it from 3.9.0 to 3.9.2 and checked in a fix.  If this is wrong,
webtools-folks, please change it.  Without the change, it would not
validate the aggregation for me.

How is it that people are getting fixes in with bugs when gerrit is
enabled?  Is there a bug in the gerrit validation testing or is it being
circumvented?

-- Jeff J.
___
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] Viatra is failing to aggregate for Photon M2 since xtext updated

[Jeff Johnston]

Thanks Abel.  Tomorrow is fine to get our patch in.  I sent a note to
the EMF Parsley and Xtext contacts
as the same error occurs for EMF Parsley.

-- Jeff J.

On Tue, Sep 19, 2017 at 4:08 PM, Ábel Hegedüs
 wrote:
> It seems Xtext has contributed 2.13.0M2 without goind through Gerrit:
>
> https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=e010159c7b3052f4695be1e156859203b8a8b742
>
> https://git.eclipse.org/r/#/q/project:simrel/org.eclipse.simrel.build
>
>
> Of course we will update the VIATRA contribution to accept Xtext 2.13,
> probably as early as tomorrow.
>
> If you are blocked, I suggest reverting the above commit.
>
>
> Best regards,
>
> -
> Ábel Hegedüs
>
> IncQuery Labs Ltd.
>
> 
> From: cross-project-issues-dev-boun...@eclipse.org
>  on behalf of Jeff Johnston
> 
> Sent: Tuesday, September 19, 2017 9:25:48 PM
> To: Cross project issues
> Cc: Zoltán Ujhelyi
> Subject: Re: [cross-project-issues-dev] Viatra is failing to aggregate for
> Photon M2 since xtext updated
>
> The error I am posting happened both when I tried validating the
> aggregation locally and when
> I submitted to gerrit.  Failure below was taken from console output
> from gerrit build job.  The log
> files do indeed note that xtext submitted a 2.13.0 update for Photon
> M2.  Perhaps the validation
> job is not using the download site you mention.
>
> -- Jeff J.
>
> On Tue, Sep 19, 2017 at 2:47 PM, Karsten Thoms  wrote:
>> The range is OK, Photon M2 contains Xtext 2.12 libraries so far. The
>> mentioned plugin org.eclipse.xtext.xbase is available in version
>> 2.12.0.v20170519-0752 on repository
>> http://download.eclipse.org/releases/photon. So I’m not sure how the problem
>> can occur. Since the bundle is there, I would not expect a problem.
>>
>> ~Karsten
>>
>>> Am 19.09.2017 um 19:29 schrieb Jeff Johnston :
>>>
>>> Xtext updated to 2.13.0.  This appears to cause Viatra to fail because
>>> it has OSGI range: [2.9.0,2.13.0)
>>>
>>> Cannot complete the install because one or more required items could
>>> not be found. Software being installed: validationSet_main 1.0.0
>>> Missing requirement: org.eclipse.viatra.query.patternlanguage
>>> 1.7.0.201708091110 requires 'bundle org.eclipse.xtext.xbase
>>> [2.9.0,2.13.0)'
>>>
>>> Not sure how the Xtext change went through gerrit validation, but I
>>> cannot push Linux Tools for Photon M2.
>>>
>>> There is another error with EMF Parsley which might be related, but I
>>> don't have the details at the moment.
>>>
>>> -- Jeff J.
>>> ___
>>> 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 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 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 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 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] EMF Parsley is failing to aggregate with new Xtext 2.13.0 update

[Jeff Johnston]

The same problem that occurs with Viatra occurs with EMF Parsley:

Cannot complete the install because one or more required items could
not be found. Software being installed: validationSet_main 1.0.0
Missing requirement: org.eclipse.emf.parsley.dsl.feature.feature.group
1.2.0.v20170608-1320 requires 'org.eclipse.xtext.xbase.feature.group
[2.12.0,2.13.0)' but it could not be found

-- Jeff J.
___
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] Viatra is failing to aggregate for Photon M2 since xtext updated

[Jeff Johnston]

The error I am posting happened both when I tried validating the
aggregation locally and when
I submitted to gerrit.  Failure below was taken from console output
from gerrit build job.  The log
files do indeed note that xtext submitted a 2.13.0 update for Photon
M2.  Perhaps the validation
job is not using the download site you mention.

-- Jeff J.

On Tue, Sep 19, 2017 at 2:47 PM, Karsten Thoms  wrote:
> The range is OK, Photon M2 contains Xtext 2.12 libraries so far. The 
> mentioned plugin org.eclipse.xtext.xbase is available in version 
> 2.12.0.v20170519-0752 on repository 
> http://download.eclipse.org/releases/photon. So I’m not sure how the problem 
> can occur. Since the bundle is there, I would not expect a problem.
>
> ~Karsten
>
>> Am 19.09.2017 um 19:29 schrieb Jeff Johnston :
>>
>> Xtext updated to 2.13.0.  This appears to cause Viatra to fail because
>> it has OSGI range: [2.9.0,2.13.0)
>>
>> Cannot complete the install because one or more required items could
>> not be found. Software being installed: validationSet_main 1.0.0
>> Missing requirement: org.eclipse.viatra.query.patternlanguage
>> 1.7.0.201708091110 requires 'bundle org.eclipse.xtext.xbase
>> [2.9.0,2.13.0)'
>>
>> Not sure how the Xtext change went through gerrit validation, but I
>> cannot push Linux Tools for Photon M2.
>>
>> There is another error with EMF Parsley which might be related, but I
>> don't have the details at the moment.
>>
>> -- Jeff J.
>> ___
>> 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 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 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] Viatra is failing to aggregate for Photon M2 since xtext updated

[Jeff Johnston]

Xtext updated to 2.13.0.  This appears to cause Viatra to fail because
it has OSGI range: [2.9.0,2.13.0)

Cannot complete the install because one or more required items could
not be found. Software being installed: validationSet_main 1.0.0
Missing requirement: org.eclipse.viatra.query.patternlanguage
1.7.0.201708091110 requires 'bundle org.eclipse.xtext.xbase
[2.9.0,2.13.0)'

Not sure how the Xtext change went through gerrit validation, but I
cannot push Linux Tools for Photon M2.

There is another error with EMF Parsley which might be related, but I
don't have the details at the moment.

-- Jeff J.
___
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] migration of existing Eclipse projects to EPL v2

[Jeff Johnston]

Hi Wayne,

Will the v2.0 license be put into
http://download.eclipse.org/cbi/updates/license/ any time soon?

-- Jeff J.

On Wed, Sep 13, 2017 at 11:58 AM, Wayne Beaton
 wrote:
> We're starting to assemble an FAQ. An answer to that question is in it.
>
> https://www.eclipse.org/org/documents/epl-2.0/faq.php
>
> Basically, a project can use the new version by simply updating the file
> headers and notices. Note that it would be good community practice to
> discuss this change on your public mailing lists, and to make every attempt
> to ensure that downstream users are aware of the change.
>
> I need to add a bit about informing the EMO so that we can update the
> project's metadata.
>
> Wayne
>
> On Wed, Sep 13, 2017 at 10:06 AM, Brian de Alwis 
> wrote:
>>
>> A follow-on question:  EPL v1.0 §7 says:
>>
>> The Program (including Contributions) may always be distributed subject to
>> the version of the Agreement under which it was received. In addition, after
>> a new version of the Agreement is published, Contributor may elect to
>> distribute the Program (including its Contributions) under the new version.
>>
>>
>> This sounds like we need to obtain permission from the contributors to use
>> EPL v2.0?
>>
>> Brian.
>>
>> On 12-Sep-2017, at 1:30 PM, Henrik Rentz-Reichert  wrote:
>>
>> Hi,
>>
>> in the last newsletter I read: „Starting immediately, the new license will
>> become the default license for Eclipse community projects.” And in the press
>> release: “The Eclipse open source project community will begin to migrate to
>> the new EPL v2. Each Eclipse project will need to go through process of
>> updating their project license and license headers to specify EPL v2. Users
>> and adopters of Eclipse projects should expect the next release of each
>> Eclipse project will be using EPL v2.”.
>>
>> Is there a Wiki page or something comparable with details on this
>> migration process?
>>
>> Thanks,
>> Henrik
>> 
>> Diese Nachricht wurde mit einer kostenlosen Version von Proxy-Manager
>> gesendet.
>> Wollen Sie von Ihrem Exchange-Konto mit einer Ihrer Proxy SMTP-Adressen
>> senden?
>> Testen Sie Proxy-Manager kostenlos!
>> Diese Fußzeile wird nicht in der registrierten Version von Proxy-Manager
>> angezeigt.
>> Klicken Sie hier, um Proxy-Manager zu registrieren.
>> ___
>> 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 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
>
>
>
>
> --
> Wayne Beaton
> Director of Open Source Projects
> The Eclipse Foundation
>
> ___
> 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 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] Linux Tools will participate in Photon (offset +3)

[Jeff Johnston]

Hi,

Linux Tools will be participating in the Eclipse Photon
release with its usual offset of +3.

The start of the release plan can be found here:

https://projects.eclipse.org/projects/tools.linuxtools/releases/7.0.0/plan

-- Jeff J.
___
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] May need a few minutes for Linux Tools RC3 contribution

[Jeff Johnston]

Ok, job just finished and I merged the change into master.

-- Jeff J.

On Wed, Jun 7, 2017 at 4:58 PM, Jeff Johnston  wrote:

> Hello,
>
> Just waiting for the gerrit validation job to go through before merging in
> the Linux Tools RC3 contribution.  I will update when it is done.
>
> -- Jeff J.
>
___
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] May need a few minutes for Linux Tools RC3 contribution

[Jeff Johnston]

Hello,

Just waiting for the gerrit validation job to go through before merging in
the Linux Tools RC3 contribution.  I will update when it is done.

-- Jeff J.
___
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] Neon.3 Update Problems: To Fix and How to Fix?

[Jeff Johnston]

FWIW:  I did a test where I removed my new Docker Tooling feature from my
EPP for committers and installed the old Neon.3 version from
the Neon repo.  This caused a number of errors as everyone else is seeing.
I then updated to the new Docker Tooling version I just merged into
org.eclipse.simrel.build
and after the update: no errors (other than a UI freeze) show up in the
error log and Docker Tooling works as well.  I was able to use some
git views without any issue.  IIRC egit was one of the reported features
with issues after Docker Tooling was installed.

-- Jeff J.

On Tue, Apr 25, 2017 at 3:31 PM, Jeff Johnston  wrote:

> Ok, I have found the problem.  The Neon site has some newer dependency
> plug-ins that were used by the docker-client 3.6.8.
> I fixed org.eclipse.linuxtools.docker.core to demand 3.4.0, but the newer
> dependencies
> were being brought in like slf4j and jackson packages since they were
> latest and greatest.
>
> I have added version ranges in docker.core for docker-client, jackson
> packages, and slf4j to lock down the versions that can
> be used.
>
> My testing was successful.  I was able to take the EPP for committers and
> install Docker Tooling on top.  No errors
> and the Docker Tooling stuff works.
>
> I have created a gerrit change that has built successfully and I have
> merged into the Neon.3_respin branch for org.eclipse.simrel.build.
>
> If anybody has experience with p2.inf files, I'd be happy to add something
> to try and help users that have already installed the
> Neon.3 Docker Tooling feature.
>
> -- Jeff J.
>
>
>
> On Tue, Apr 25, 2017 at 12:09 PM, Jeff Johnston 
> wrote:
>
>> Should we add uninstallbundle commands in the p2.inf file for the Docker
>> Tooling feature to remove all the http bundles
>> that might have been installed by a previous version?  I have found
>> another problem when installing the Docker tooling
>> feature from the new aggregation on top of the Neon.3 EPP for Eclipse
>> committers.  Multiple slf4j bundles cause a gradle failure.
>> I am working on a fix now.  I can add the p2.inf stuff at the same time
>> if deemed useful.
>>
>> -- Jeff J.
>>
>> On Tue, Apr 25, 2017 at 11:19 AM, Ed Merks  wrote:
>>
>>> Fred,
>>>
>>> No I didn't try that.  It's much harder to try that.  Oomph itself is
>>> broken, so I can't run setup tasks.  Check for Updates finds no updates
>>> because I installed all the categories and their IUs don't have updated
>>> versions.   I tried explicitly installing Docker so that it would do an
>>> update, but that didn't not solve the wiring problem.  I also running the
>>> p2 task in an IDE with Oomph 1.8 where I can run setup tasks (because
>>> Oomph's dependency on userstorage is optional in 1.8) and where the wiring
>>> problems also occurred so that more things got updated, but this also did
>>> not resolve the wiring problem.  So it's not clear if updates to an already
>>> -broken IDE will fix that IDE; it doesn't look so promising, though I don't
>>> understand why that wouldn't work.   If nothing requires a given bundle, I
>>> would expect that bundle to be removed from the profile, but I don't see
>>> the problematic bundles being removed...
>>>
>>> Regards,
>>> Ed
>>>
>>>
>>> On 25.04.2017 16:41, Frederic Gurr wrote:
>>>
>>>> Thanks Ed.
>>>>
>>>> That sounds promising. Did you also test updating a broken ELWMS with
>>>> the new repo?
>>>>
>>>> I'm currently trying to reproduce the error with EPP packages, but so
>>>> far updating a Neon.2 package to Neon.3 (with "Check for Updates") did
>>>> not result in a broken MPC. Not sure what I'm missing.
>>>>
>>>> Regards,
>>>>
>>>> Fred
>>>>
>>>> On 25.04.2017 16:30, Ed Merks wrote:
>>>>
>>>>> Fred,
>>>>>
>>>>> Installing the Eierlegende Wollmilchsau with this additional repository
>>>>> in the p2 task's repository list results in an installation without
>>>>> wiring problems.
>>>>>
>>>>> The profile of the installation contains version 2.3.0.20170421191 of
>>>>> org.eclipse.linuxtools.docker.core with is indeed the version
>>>>> available
>>>>> in
>>>>> https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.r
>>>>> unaggregator.BUILD__CLEAN/3/artifact/aggregation/final
&g

Re: [cross-project-issues-dev] Neon.3 Update Problems: To Fix and How to Fix?

[Jeff Johnston]

Ok, I have found the problem.  The Neon site has some newer dependency
plug-ins that were used by the docker-client 3.6.8.
I fixed org.eclipse.linuxtools.docker.core to demand 3.4.0, but the newer
dependencies
were being brought in like slf4j and jackson packages since they were
latest and greatest.

I have added version ranges in docker.core for docker-client, jackson
packages, and slf4j to lock down the versions that can
be used.

My testing was successful.  I was able to take the EPP for committers and
install Docker Tooling on top.  No errors
and the Docker Tooling stuff works.

I have created a gerrit change that has built successfully and I have
merged into the Neon.3_respin branch for org.eclipse.simrel.build.

If anybody has experience with p2.inf files, I'd be happy to add something
to try and help users that have already installed the
Neon.3 Docker Tooling feature.

-- Jeff J.



On Tue, Apr 25, 2017 at 12:09 PM, Jeff Johnston  wrote:

> Should we add uninstallbundle commands in the p2.inf file for the Docker
> Tooling feature to remove all the http bundles
> that might have been installed by a previous version?  I have found
> another problem when installing the Docker tooling
> feature from the new aggregation on top of the Neon.3 EPP for Eclipse
> committers.  Multiple slf4j bundles cause a gradle failure.
> I am working on a fix now.  I can add the p2.inf stuff at the same time if
> deemed useful.
>
> -- Jeff J.
>
> On Tue, Apr 25, 2017 at 11:19 AM, Ed Merks  wrote:
>
>> Fred,
>>
>> No I didn't try that.  It's much harder to try that.  Oomph itself is
>> broken, so I can't run setup tasks.  Check for Updates finds no updates
>> because I installed all the categories and their IUs don't have updated
>> versions.   I tried explicitly installing Docker so that it would do an
>> update, but that didn't not solve the wiring problem.  I also running the
>> p2 task in an IDE with Oomph 1.8 where I can run setup tasks (because
>> Oomph's dependency on userstorage is optional in 1.8) and where the wiring
>> problems also occurred so that more things got updated, but this also did
>> not resolve the wiring problem.  So it's not clear if updates to an already
>> -broken IDE will fix that IDE; it doesn't look so promising, though I don't
>> understand why that wouldn't work.   If nothing requires a given bundle, I
>> would expect that bundle to be removed from the profile, but I don't see
>> the problematic bundles being removed...
>>
>> Regards,
>> Ed
>>
>>
>> On 25.04.2017 16:41, Frederic Gurr wrote:
>>
>>> Thanks Ed.
>>>
>>> That sounds promising. Did you also test updating a broken ELWMS with
>>> the new repo?
>>>
>>> I'm currently trying to reproduce the error with EPP packages, but so
>>> far updating a Neon.2 package to Neon.3 (with "Check for Updates") did
>>> not result in a broken MPC. Not sure what I'm missing.
>>>
>>> Regards,
>>>
>>> Fred
>>>
>>> On 25.04.2017 16:30, Ed Merks wrote:
>>>
>>>> Fred,
>>>>
>>>> Installing the Eierlegende Wollmilchsau with this additional repository
>>>> in the p2 task's repository list results in an installation without
>>>> wiring problems.
>>>>
>>>> The profile of the installation contains version 2.3.0.20170421191 of
>>>> org.eclipse.linuxtools.docker.core with is indeed the version available
>>>> in
>>>> https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.r
>>>> unaggregator.BUILD__CLEAN/3/artifact/aggregation/final
>>>> so I think this is a good demonstration that installations creation from
>>>> this repository's contents will not have the wiring problems we've been
>>>> seeing in Neon.3.
>>>>
>>>> Regards,
>>>> Ed
>>>>
>>>>
>>>> Ed,
>>>>>
>>>>> The temporary update site URL is:
>>>>>
>>>>> https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.r
>>>>> unaggregator.BUILD__CLEAN/3/artifact/aggregation/final
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Fred
>>>>>
>>>>> On 25.04.2017 15:13, Ed Merks wrote:
>>>>>
>>>>>> Fred,
>>>>>>
>>>>>> What update site URL contains these results?
>>>>>>
>>>>>> Regards,
>>>>>> Ed
>>&g

Re: [cross-project-issues-dev] Neon.3 Update Problems: To Fix and How to Fix?

[Jeff Johnston]

Should we add uninstallbundle commands in the p2.inf file for the Docker
Tooling feature to remove all the http bundles
that might have been installed by a previous version?  I have found another
problem when installing the Docker tooling
feature from the new aggregation on top of the Neon.3 EPP for Eclipse
committers.  Multiple slf4j bundles cause a gradle failure.
I am working on a fix now.  I can add the p2.inf stuff at the same time if
deemed useful.

-- Jeff J.

On Tue, Apr 25, 2017 at 11:19 AM, Ed Merks  wrote:

> Fred,
>
> No I didn't try that.  It's much harder to try that.  Oomph itself is
> broken, so I can't run setup tasks.  Check for Updates finds no updates
> because I installed all the categories and their IUs don't have updated
> versions.   I tried explicitly installing Docker so that it would do an
> update, but that didn't not solve the wiring problem.  I also running the
> p2 task in an IDE with Oomph 1.8 where I can run setup tasks (because
> Oomph's dependency on userstorage is optional in 1.8) and where the wiring
> problems also occurred so that more things got updated, but this also did
> not resolve the wiring problem.  So it's not clear if updates to an already
> -broken IDE will fix that IDE; it doesn't look so promising, though I don't
> understand why that wouldn't work.   If nothing requires a given bundle, I
> would expect that bundle to be removed from the profile, but I don't see
> the problematic bundles being removed...
>
> Regards,
> Ed
>
>
> On 25.04.2017 16:41, Frederic Gurr wrote:
>
>> Thanks Ed.
>>
>> That sounds promising. Did you also test updating a broken ELWMS with
>> the new repo?
>>
>> I'm currently trying to reproduce the error with EPP packages, but so
>> far updating a Neon.2 package to Neon.3 (with "Check for Updates") did
>> not result in a broken MPC. Not sure what I'm missing.
>>
>> Regards,
>>
>> Fred
>>
>> On 25.04.2017 16:30, Ed Merks wrote:
>>
>>> Fred,
>>>
>>> Installing the Eierlegende Wollmilchsau with this additional repository
>>> in the p2 task's repository list results in an installation without
>>> wiring problems.
>>>
>>> The profile of the installation contains version 2.3.0.20170421191 of
>>> org.eclipse.linuxtools.docker.core with is indeed the version available
>>> in
>>> https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.
>>> runaggregator.BUILD__CLEAN/3/artifact/aggregation/final
>>> so I think this is a good demonstration that installations creation from
>>> this repository's contents will not have the wiring problems we've been
>>> seeing in Neon.3.
>>>
>>> Regards,
>>> Ed
>>>
>>>
>>> Ed,
>>>>
>>>> The temporary update site URL is:
>>>>
>>>> https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.
>>>> runaggregator.BUILD__CLEAN/3/artifact/aggregation/final
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Fred
>>>>
>>>> On 25.04.2017 15:13, Ed Merks wrote:
>>>>
>>>>> Fred,
>>>>>
>>>>> What update site URL contains these results?
>>>>>
>>>>> Regards,
>>>>> Ed
>>>>>
>>>>>
>>>>> On 25.04.2017 14:28, Frederic Gurr wrote:
>>>>>
>>>>>> Thanks Jeff,
>>>>>>
>>>>>> This is the comparison of the non-unique versions list:
>>>>>>
>>>>>> neon3_respin aggregation build 20.04.
>>>>>> (https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.
>>>>>> runaggregator.BUILD__CLEAN/2/artifact/aggregation/final/
>>>>>> buildInfo/reporeports/reports/nonUniqueVersions.txt):
>>>>>>
>>>>>>
>>>>>>
>>>>>> org.apache.httpcomponents.httpclient
>>>>>>   4.3.6.v201411290715
>>>>>>   4.5.2.v20161115-1643
>>>>>>   4.3.6.v201511171540
>>>>>>   4.2.6.v201311072007
>>>>>> org.apache.httpcomponents.httpcore
>>>>>>   4.3.3.v201411290715
>>>>>>   4.4.6.v20170210-0925
>>>>>>   4.2.5.v201311072007
>>>>>>   neon3_respin aggregation build 25.04.
>>>>>> (https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.
>>>>>

Re: [cross-project-issues-dev] Neon.3 Update Problems: To Fix and How to Fix?

[Jeff Johnston]

Just to confirm that the change has been merged to the Neon.3_respin branch.

-- Jeff J.

On Fri, Apr 21, 2017 at 4:11 PM, Jeff Johnston  wrote:

> I have done another respin.  In this case, I rebuilt the Linux Tools
> plug-ins to use the older version
> of docker-client and its dependencies which were used in Neon.2.  I have
> back-versioned the
> Docker tooling plug-ins to 2.3.0 with the current date.
>
> I have just pushed to gerrit for Neon.3_respin branch.
>
> https://git.eclipse.org/r/#/c/95501/
>
> If no-one objects, I will merge into the branch.  Verification is already
> successful.
>
> -- Jeff J.
>
> On Fri, Apr 21, 2017 at 11:50 AM, Jeff Johnston 
> wrote:
>
>> Marcel,
>>
>> Since the respin didn't fix the problem, we will try reverting the
>> docker-client dependency and keeping as much of the added Neon.3
>> functionality as possible
>> in place and cutting another point release.  I will let the list know
>> when I have something in place.
>>
>> -- Jeff J.
>>
>> On Fri, Apr 21, 2017 at 6:38 AM, Daniel Megert 
>> wrote:
>>
>>> Adding eclipse.org-planning-coun...@eclipse.org to this thread.
>>>
>>> Dani
>>>
>>>
>>>
>>> From:"Dr. Marcel Bruch" 
>>> To:Cross project issues 
>>> Date:21.04.2017 10:17
>>> Subject:Re: [cross-project-issues-dev] Neon.3 Update Problems:
>>> To Fix andHow to Fix?
>>> Sent by:cross-project-issues-dev-boun...@eclipse.org
>>> --
>>>
>>>
>>>
>>> Hi,
>>>
>>> I’ll briefly summarize the discussion we had at the AC yesterday:
>>>
>>> Given that we don’t know how the OSGI resolver will behave (even after
>>> Tom back-ported a fix to Neon) it would be preferred to just have the
>>> Apache HTTP*** versions in Neon.3 that were already in Neon.2. This would
>>> to some extend “ensure" that we are "at least as as stable as Neon.2”. This
>>> would require us to rollback the changes that introduced the latest version
>>> of HTTPClient. As far as I know this would especially affect the Docker
>>> Tooling. (maybe more changes than that are needed)
>>>
>>> My question to the *Docker Tooling project lead*: Is it possible to
>>> rollback this last minute change and postpone it to Oxygen for the sake of
>>> making EGit, MPC, Oomph, USS, and Code Recommenders work reliably again -
>>> and giving us more trust that we won’t get into trouble with Neon.3? The
>>> simplest solution may be to contribute the docker tooling from Neon.2 in
>>> Neon.3. WDYT?
>>>
>>> Marcel
>>>
>>>
>>>
>>>
>>> On 20 Apr 2017, at 18:54, Frederic Gurr <*frederic.g...@eclipse.org*
>>> > wrote:
>>>
>>> I can see org.apache.httpcomponents.httpclient_4.5.2.v20170210-0925 in
>>> /home/data/httpd/
>>> *download.eclipse.org/linuxtools/update-docker-2.3.1/plugins*
>>> <http://download.eclipse.org/linuxtools/update-docker-2.3.1/plugins>,
>>> but it's definitely not in the aggregated repo.
>>>
>>>
>>> On 20.04.2017 18:31, Jeff Johnston wrote:
>>> Fred,
>>>
>>> The version of httpclient also changed in our update-docker-2.3.1 repo
>>> from:
>>>
>>> org.apache.httpcomponents.httpclient_4.5.2.v20161115-1643
>>>
>>> to:
>>>
>>> org.apache.httpcomponents.httpclient_4.5.2.v20170210-0925
>>>
>>> Not sure why this change isn't being seen as well.
>>>
>>> -- Jeff J.
>>>
>>>
>>>
>>> On Thu, Apr 20, 2017 at 12:21 PM, Frederic Gurr
>>> <*frederic.g...@eclipse.org* <
>>> *mailto:frederic.g...@eclipse.org* >> wrote:
>>>
>>>   Thanks Jeff,
>>>
>>>   I ran a SimRel aggregation build. The only change I can see in the list
>>>   of "Non Unique Versions used in repository" is that a different version
>>>   of org.apache.httpcomponents.httpcore is now used. Instead of
>>>   4.4.4.v20161115-1643 it's now 4.4.6.v20170210-0925.
>>>
>>>   I compared
>>>
>>> *http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt*
>>> <http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt>
>>>   <
>>> *http://download.eclipse.org/re

Re: [cross-project-issues-dev] Neon.3 Update Problems: To Fix and How to Fix?

[Jeff Johnston]

I have done another respin.  In this case, I rebuilt the Linux Tools
plug-ins to use the older version
of docker-client and its dependencies which were used in Neon.2.  I have
back-versioned the
Docker tooling plug-ins to 2.3.0 with the current date.

I have just pushed to gerrit for Neon.3_respin branch.

https://git.eclipse.org/r/#/c/95501/

If no-one objects, I will merge into the branch.  Verification is already
successful.

-- Jeff J.

On Fri, Apr 21, 2017 at 11:50 AM, Jeff Johnston  wrote:

> Marcel,
>
> Since the respin didn't fix the problem, we will try reverting the
> docker-client dependency and keeping as much of the added Neon.3
> functionality as possible
> in place and cutting another point release.  I will let the list know when
> I have something in place.
>
> -- Jeff J.
>
> On Fri, Apr 21, 2017 at 6:38 AM, Daniel Megert 
> wrote:
>
>> Adding eclipse.org-planning-coun...@eclipse.org to this thread.
>>
>> Dani
>>
>>
>>
>> From:"Dr. Marcel Bruch" 
>> To:Cross project issues 
>> Date:21.04.2017 10:17
>> Subject:Re: [cross-project-issues-dev] Neon.3 Update Problems:
>> To Fix andHow to Fix?
>> Sent by:cross-project-issues-dev-boun...@eclipse.org
>> --
>>
>>
>>
>> Hi,
>>
>> I’ll briefly summarize the discussion we had at the AC yesterday:
>>
>> Given that we don’t know how the OSGI resolver will behave (even after
>> Tom back-ported a fix to Neon) it would be preferred to just have the
>> Apache HTTP*** versions in Neon.3 that were already in Neon.2. This would
>> to some extend “ensure" that we are "at least as as stable as Neon.2”. This
>> would require us to rollback the changes that introduced the latest version
>> of HTTPClient. As far as I know this would especially affect the Docker
>> Tooling. (maybe more changes than that are needed)
>>
>> My question to the *Docker Tooling project lead*: Is it possible to
>> rollback this last minute change and postpone it to Oxygen for the sake of
>> making EGit, MPC, Oomph, USS, and Code Recommenders work reliably again -
>> and giving us more trust that we won’t get into trouble with Neon.3? The
>> simplest solution may be to contribute the docker tooling from Neon.2 in
>> Neon.3. WDYT?
>>
>> Marcel
>>
>>
>>
>>
>> On 20 Apr 2017, at 18:54, Frederic Gurr <*frederic.g...@eclipse.org*
>> > wrote:
>>
>> I can see org.apache.httpcomponents.httpclient_4.5.2.v20170210-0925 in
>> /home/data/httpd/
>> *download.eclipse.org/linuxtools/update-docker-2.3.1/plugins*
>> <http://download.eclipse.org/linuxtools/update-docker-2.3.1/plugins>,
>> but it's definitely not in the aggregated repo.
>>
>>
>> On 20.04.2017 18:31, Jeff Johnston wrote:
>> Fred,
>>
>> The version of httpclient also changed in our update-docker-2.3.1 repo
>> from:
>>
>> org.apache.httpcomponents.httpclient_4.5.2.v20161115-1643
>>
>> to:
>>
>> org.apache.httpcomponents.httpclient_4.5.2.v20170210-0925
>>
>> Not sure why this change isn't being seen as well.
>>
>> -- Jeff J.
>>
>>
>>
>> On Thu, Apr 20, 2017 at 12:21 PM, Frederic Gurr
>> <*frederic.g...@eclipse.org* <
>> *mailto:frederic.g...@eclipse.org* >> wrote:
>>
>>   Thanks Jeff,
>>
>>   I ran a SimRel aggregation build. The only change I can see in the list
>>   of "Non Unique Versions used in repository" is that a different version
>>   of org.apache.httpcomponents.httpcore is now used. Instead of
>>   4.4.4.v20161115-1643 it's now 4.4.6.v20170210-0925.
>>
>>   I compared
>>
>> *http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt*
>> <http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt>
>>   <
>> *http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt*
>> <http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt>
>> >
>>   and
>>
>> *https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/ws/aggregation/final/buildInfo/reporeports/reports/nonUniqueVersions.txt*
>> <https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/ws/aggregation/final/buildInfo/reporeports/reports/nonUniqueVersions.txt>
>>   <
>> *https://h

Re: [cross-project-issues-dev] Neon.3 Update Problems: To Fix and How to Fix?

[Jeff Johnston]

Marcel,

Since the respin didn't fix the problem, we will try reverting the
docker-client dependency and keeping as much of the added Neon.3
functionality as possible
in place and cutting another point release.  I will let the list know when
I have something in place.

-- Jeff J.

On Fri, Apr 21, 2017 at 6:38 AM, Daniel Megert 
wrote:

> Adding eclipse.org-planning-coun...@eclipse.org to this thread.
>
> Dani
>
>
>
> From:"Dr. Marcel Bruch" 
> To:Cross project issues 
> Date:21.04.2017 10:17
> Subject:Re: [cross-project-issues-dev] Neon.3 Update Problems: To
> Fix andHow to Fix?
> Sent by:cross-project-issues-dev-boun...@eclipse.org
> --
>
>
>
> Hi,
>
> I’ll briefly summarize the discussion we had at the AC yesterday:
>
> Given that we don’t know how the OSGI resolver will behave (even after Tom
> back-ported a fix to Neon) it would be preferred to just have the Apache
> HTTP*** versions in Neon.3 that were already in Neon.2. This would to some
> extend “ensure" that we are "at least as as stable as Neon.2”. This would
> require us to rollback the changes that introduced the latest version of
> HTTPClient. As far as I know this would especially affect the Docker
> Tooling. (maybe more changes than that are needed)
>
> My question to the *Docker Tooling project lead*: Is it possible to
> rollback this last minute change and postpone it to Oxygen for the sake of
> making EGit, MPC, Oomph, USS, and Code Recommenders work reliably again -
> and giving us more trust that we won’t get into trouble with Neon.3? The
> simplest solution may be to contribute the docker tooling from Neon.2 in
> Neon.3. WDYT?
>
> Marcel
>
>
>
>
> On 20 Apr 2017, at 18:54, Frederic Gurr <*frederic.g...@eclipse.org*
> > wrote:
>
> I can see org.apache.httpcomponents.httpclient_4.5.2.v20170210-0925 in
> /home/data/httpd/
> *download.eclipse.org/linuxtools/update-docker-2.3.1/plugins*
> <http://download.eclipse.org/linuxtools/update-docker-2.3.1/plugins>,
> but it's definitely not in the aggregated repo.
>
>
> On 20.04.2017 18:31, Jeff Johnston wrote:
> Fred,
>
> The version of httpclient also changed in our update-docker-2.3.1 repo
> from:
>
> org.apache.httpcomponents.httpclient_4.5.2.v20161115-1643
>
> to:
>
> org.apache.httpcomponents.httpclient_4.5.2.v20170210-0925
>
> Not sure why this change isn't being seen as well.
>
> -- Jeff J.
>
>
>
> On Thu, Apr 20, 2017 at 12:21 PM, Frederic Gurr
> <*frederic.g...@eclipse.org* <
> *mailto:frederic.g...@eclipse.org* >> wrote:
>
>   Thanks Jeff,
>
>   I ran a SimRel aggregation build. The only change I can see in the list
>   of "Non Unique Versions used in repository" is that a different version
>   of org.apache.httpcomponents.httpcore is now used. Instead of
>   4.4.4.v20161115-1643 it's now 4.4.6.v20170210-0925.
>
>   I compared
>
> *http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt*
> <http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt>
>   <
> *http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt*
> <http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt>
> >
>   and
>
> *https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/ws/aggregation/final/buildInfo/reporeports/reports/nonUniqueVersions.txt*
> <https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/ws/aggregation/final/buildInfo/reporeports/reports/nonUniqueVersions.txt>
>   <
> *https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/ws/aggregation/final/buildInfo/reporeports/reports/nonUniqueVersions.txt*
> <https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/ws/aggregation/final/buildInfo/reporeports/reports/nonUniqueVersions.txt>
> >
>
>   @All: is that the intended result?
>
>   Regards,
>
>   Fred
>
>
>   On 19.04.2017 20:21, Jeff Johnston wrote:
> Hi Fred,
>
> I have just pushed a change to gerrit:
>*https://git.eclipse.org/r/#/c/95308/*
> <https://git.eclipse.org/r/#/c/95308/>
>   <*https://git.eclipse.org/r/#/c/95308/*
> <https://git.eclipse.org/r/#/c/95308/>>
>
> I only changed the docker repository and left the other Linux Tools
> features alone
> since they were only bumped as part of the point release to fix the
> Docker Tooling

Re: [cross-project-issues-dev] Neon.3 Update Problems: To Fix and How to Fix?

[Jeff Johnston]

Fred,

The version of httpclient also changed in our update-docker-2.3.1 repo from:

org.apache.httpcomponents.httpclient_4.5.2.v20161115-1643

to:

org.apache.httpcomponents.httpclient_4.5.2.v20170210-0925

Not sure why this change isn't being seen as well.

-- Jeff J.



On Thu, Apr 20, 2017 at 12:21 PM, Frederic Gurr 
wrote:

> Thanks Jeff,
>
> I ran a SimRel aggregation build. The only change I can see in the list
> of "Non Unique Versions used in repository" is that a different version
> of org.apache.httpcomponents.httpcore is now used. Instead of
> 4.4.4.v20161115-1643 it's now 4.4.6.v20170210-0925.
>
> I compared
> http://download.eclipse.org/releases/neon/201703231000/
> buildInfo/reporeports/reports/nonUniqueVersions.txt
> and
> https://hudson.eclipse.org/simrel/job/simrel.neon.3_
> respin.runaggregator.BUILD__CLEAN/ws/aggregation/final/
> buildInfo/reporeports/reports/nonUniqueVersions.txt
>
> @All: is that the intended result?
>
> Regards,
>
> Fred
>
>
> On 19.04.2017 20:21, Jeff Johnston wrote:
> > Hi Fred,
> >
> > I have just pushed a change to gerrit: https://git.eclipse.org/r/#/c/
> 95308/
> >
> > I only changed the docker repository and left the other Linux Tools
> > features alone
> > since they were only bumped as part of the point release to fix the
> > Docker Tooling plug-ins.
> >
> > I assume I can merge the patch if the gerrit verification is
> > successful.  If this is wrong,
> > let me know.
> >
> > -- Jeff J.
> >
> > On Wed, Apr 19, 2017 at 1:08 PM, Frederic Gurr
> > mailto:frederic.g...@eclipse.org>> wrote:
> >
> > Hi,
> >
> > Can you provide a patch for the SimRel build (branch "Neon.3_respin")
> > that references the new version?
> >
> > Regards,
> >
> > Fred
> >
> > On 19.04.2017 17:27, Jeff Johnston wrote:
> > > Hi Ed,
> > >
> > > Linux tools spun a 5.3.1 release which now has a 2.3.1 version of
> > docker
> > > tooling.  The Linux tools download site has update-docker-2.3.1 and
> > > update-docker, both which have 2.3.1 versions of the docker.core
> > plug-in
> > > and docker feature.  Not sure why you are not seeing this.
> > >
> > > -- Jeff J.
> > >
> > > On Wed, Apr 19, 2017 at 11:13 AM, Ed Merks  > <mailto:ed.me...@gmail.com>
> > > <mailto:ed.me...@gmail.com <mailto:ed.me...@gmail.com>>> wrote:
> > >
> > > Frederic,
> > >
> > > There seem to have been no notes/minutes taken during the
> meeting:
> > >
> > >   https://wiki.eclipse.org/Planning_Council/April_05_2017
> > <https://wiki.eclipse.org/Planning_Council/April_05_2017>
> > > <https://wiki.eclipse.org/Planning_Council/April_05_2017
> > <https://wiki.eclipse.org/Planning_Council/April_05_2017>>
> > >
> > > I recall agreeing to provide steps for reproducing the problem
> so
> > > that Thomas Watson could test if the wiring resolution fix he
> made
> > > for Oxygen also solves the problem for Neon.3.  The fact that
> he
> > > encountered "the mirroring problem" didn't help in that regard:
> > >
> > >   https://bugs.eclipse.org/bugs/show_bug.cgi?id=515213
> > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=515213>
> > > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=515213
> > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=515213>>
> > >
> > > In the end, he sent me a note saying (and I quote):
> > >
> > >> I see that now there is the same number of httpcomponents
> bundles
> > >> as there was in the messed up Oxygen M6 builds.  But here my
> back
> > >> port of the resolver fix does not seem to have fixed the
> issue.
> > >> I'm unsure if that is because it gave up with the sheer
> number of
> > >> bundles or if something else is going wrong.  But at this
> point
> > >> the backport of the resolver fix does not seem to be the
> solution
> > >> to the problem.
> > >
> > > I assumed (wrongly I guess) that Thomas would investigate a
> more
> > > general fix to address the wiring problem.
> > >
> > > In the end, I also wasn'

Re: [cross-project-issues-dev] Neon.3 Update Problems: To Fix and How to Fix?

[Jeff Johnston]

Hi Fred,

I have just pushed a change to gerrit: https://git.eclipse.org/r/#/c/95308/

I only changed the docker repository and left the other Linux Tools
features alone
since they were only bumped as part of the point release to fix the Docker
Tooling plug-ins.

I assume I can merge the patch if the gerrit verification is successful.
If this is wrong,
let me know.

-- Jeff J.

On Wed, Apr 19, 2017 at 1:08 PM, Frederic Gurr 
wrote:

> Hi,
>
> Can you provide a patch for the SimRel build (branch "Neon.3_respin")
> that references the new version?
>
> Regards,
>
> Fred
>
> On 19.04.2017 17:27, Jeff Johnston wrote:
> > Hi Ed,
> >
> > Linux tools spun a 5.3.1 release which now has a 2.3.1 version of docker
> > tooling.  The Linux tools download site has update-docker-2.3.1 and
> > update-docker, both which have 2.3.1 versions of the docker.core plug-in
> > and docker feature.  Not sure why you are not seeing this.
> >
> > -- Jeff J.
> >
> > On Wed, Apr 19, 2017 at 11:13 AM, Ed Merks  > <mailto:ed.me...@gmail.com>> wrote:
> >
> > Frederic,
> >
> > There seem to have been no notes/minutes taken during the meeting:
> >
> >   https://wiki.eclipse.org/Planning_Council/April_05_2017
> > <https://wiki.eclipse.org/Planning_Council/April_05_2017>
> >
> > I recall agreeing to provide steps for reproducing the problem so
> > that Thomas Watson could test if the wiring resolution fix he made
> > for Oxygen also solves the problem for Neon.3.  The fact that he
> > encountered "the mirroring problem" didn't help in that regard:
> >
> >   https://bugs.eclipse.org/bugs/show_bug.cgi?id=515213
> > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=515213>
> >
> > In the end, he sent me a note saying (and I quote):
> >
> >> I see that now there is the same number of httpcomponents bundles
> >> as there was in the messed up Oxygen M6 builds.  But here my back
> >> port of the resolver fix does not seem to have fixed the issue.
> >> I'm unsure if that is because it gave up with the sheer number of
> >> bundles or if something else is going wrong.  But at this point
> >> the backport of the resolver fix does not seem to be the solution
> >> to the problem.
> >
> > I assumed (wrongly I guess) that Thomas would investigate a more
> > general fix to address the wiring problem.
> >
> > In the end, I also wasn't sure which version of the docker tools is
> > proposed for contribution to Neon.3a.  I tried to search for update
> > sites containing it like this:
> >
> > Nothing looks like a new version of 2.3.  Goodness knows where one
> > should find what's being proposed for contribution...
> >
> > In any case, the proposed "solution" (A) really just changes the
> > version of httpclient to be one that's not broken (missing
> > packages), but it doesn't change the wiring problem in any
> > fundamental way.  There will still be the four versions that can all
> > be installed simultaneously, so we really should expect the same
> > wiring problem(s).  In fact, I believe Oxygen M6 has effectively the
> > same four httpcomponents.httpclient bundle as does Neon.3, so I'm a
> > little suspicious whether the wiring problem is in fact really fixed
> > even for Oxygen.  We won't know until M7 and that's a month away.
> > It doesn't give me warm fuzzy feelings.
> >
> > So at this point it remains unclear the nature of the wiring
> > problem(s).  Is it a bug? Is it fixable? Does the knowledge, will,
> > and capacity to fix it exist?
> >
> > Without a fix to the wiring problem I think we can eliminate A as a
> > solution, leaving B, C, and D (i.e., focus on problem avoidance
> > approaches).  But I think if the wiring problem is a bug, it will
> > come back, and it will raise its ugly head again when users install
> > various technologies from various sources.  To my thinking, fixing
> > the bug seems important.
> >
> > Regards,
> > Ed
> >
> >
> > On 19.04.2017 12:49, Frederic Gurr wrote:
> >> Hi Ed,
> >>
> >> In the last planning-council meeting you offered to evaluate if the
> >> fixed Linux Tools package works as expected and if there are still
> >> wiring issues.
> >>
> >> Can you give us an update on 

Re: [cross-project-issues-dev] Neon.3 Update Problems: To Fix and How to Fix?

[Jeff Johnston]

Hi Ed,

Linux tools spun a 5.3.1 release which now has a 2.3.1 version of docker
tooling.  The Linux tools download site has update-docker-2.3.1 and
update-docker, both which have 2.3.1 versions of the docker.core plug-in
and docker feature.  Not sure why you are not seeing this.

-- Jeff J.

On Wed, Apr 19, 2017 at 11:13 AM, Ed Merks  wrote:

> Frederic,
>
> There seem to have been no notes/minutes taken during the meeting:
>
>   https://wiki.eclipse.org/Planning_Council/April_05_2017
> I recall agreeing to provide steps for reproducing the problem so that
> Thomas Watson could test if the wiring resolution fix he made for Oxygen
> also solves the problem for Neon.3.  The fact that he encountered "the
> mirroring problem" didn't help in that regard:
>
>   https://bugs.eclipse.org/bugs/show_bug.cgi?id=515213
>
> In the end, he sent me a note saying (and I quote):
>
> I see that now there is the same number of httpcomponents bundles as there
> was in the messed up Oxygen M6 builds.  But here my back port of the
> resolver fix does not seem to have fixed the issue.  I'm unsure if that is
> because it gave up with the sheer number of bundles or if something else is
> going wrong.  But at this point the backport of the resolver fix does not
> seem to be the solution to the problem.
>
>
> I assumed (wrongly I guess) that Thomas would investigate a more general
> fix to address the wiring problem.
>
> In the end, I also wasn't sure which version of the docker tools is
> proposed for contribution to Neon.3a.  I tried to search for update sites
> containing it like this:
>
> Nothing looks like a new version of 2.3.  Goodness knows where one should
> find what's being proposed for contribution...
>
> In any case, the proposed "solution" (A) really just changes the version
> of httpclient to be one that's not broken (missing packages), but it
> doesn't change the wiring problem in any fundamental way.  There will still
> be the four versions that can all be installed simultaneously, so we really
> should expect the same wiring problem(s).  In fact, I believe Oxygen M6 has
> effectively the same four httpcomponents.httpclient bundle as does Neon.3,
> so I'm a little suspicious whether the wiring problem is in fact really
> fixed even for Oxygen.  We won't know until M7 and that's a month away.  It
> doesn't give me warm fuzzy feelings.
>
> So at this point it remains unclear the nature of the wiring problem(s).
> Is it a bug? Is it fixable? Does the knowledge, will, and capacity to fix
> it exist?
>
> Without a fix to the wiring problem I think we can eliminate A as a
> solution, leaving B, C, and D (i.e., focus on problem avoidance
> approaches).  But I think if the wiring problem is a bug, it will come
> back, and it will raise its ugly head again when users install various
> technologies from various sources.  To my thinking, fixing the bug seems
> important.
>
> Regards,
> Ed
>
>
> On 19.04.2017 12:49, Frederic Gurr wrote:
>
> Hi Ed,
>
> In the last planning-council meeting you offered to evaluate if the
> fixed Linux Tools package works as expected and if there are still
> wiring issues.
>
> Can you give us an update on the current state?
>
> Regards,
>
> Fred
>
> On 31.03.2017 11:14, Ed Merks wrote:
>
> Hi,
>
> The original thread is fractured into many threads so its kind of
> impossible to follow each thread with a reply but I'll try at the bottom
> of this note, i.e., below the ===
>
> But before doing that, I'd like to re-focus on the most important
> questions: *We currently have a problem with Neon.3, will we fix it, and
> if so how will we fix it?*
>
> The discussion has quickly digressed (constructively) into solving the
> issue of how Orbit dependencies should be managed by projects and by the
> release train.  Unfortunately I see this as a world hunger issue; not
> one that is easily addressed and I believe not one we can wait for in
> order to solve the Neon.3 problem.  Let's face it, we've not been able
> to produce a proper Oxygen milestone in months, we still don't have one
> now, and we won't have one until next month, we hope.
>
> For Neon we've done three maintenance releases.  Neon.1 needed a respin
> and Neon.3 looks to be in need of the same thing.  Clearly something is
> seriously wrong.  But if we spend our time on solving the Orbit world
> hunger issue, will we arrive at a solution in time for Oxygen, let alone
> in time to fix Neon.3?  I am very, very doubtful.
>
> As another data point, if I install the egg-laying-wool-milk-pig for
> Neon.3.  The following happens.  I'm prompted to accept this license:
>
> Red Hat, Inc. licenses these features and plugins to you under
> certain open source licenses (or aggregations of such licenses),
> which in a particular case may include the Eclipse Public License,
> the GNU Lesser General Public License, and/or certain other open
> source licenses. For precise licensing details, consult the
> corresponding source code

Re: [cross-project-issues-dev] Neon.3 Update Problems

[Jeff Johnston]

Switching to Neon.3 orbit won't solve the problem as the 3.6.8
docker-client there will still result in pulling in the newer httpclient
which is also in the Neon.3 orbit repo.

I have respun the Linux Tools to create a 5.3.1 release with the updated
packages.  If a re-aggregation will occur and I need to change the 
linuxtools.b3aggrcon file
for Neon maintenance, someone let me know.

-- Jeff J.

- Original Message -
> Well, the good news is that the httpclient 4.5 bundle didn't make it into any
> of the packages as far as I can see.
> 
> I've just had a look at the latest Neon repository metadata, and there are a
> lot of bundles that require a httpclient < 4.5 [1], and apparently only
> Linux Tools, that (by way of the Jersey Apache Connector) requires
> httpclient >= 4.5 [2]. I think the safe bet would be for Linux Tools to do a
> release that uses the Neon Orbit to get rid of the newer httpclient if
> that's possible.
> 
> While in theory the two httpclient bundles should be able to work
> side-by-side, we've seen a lot of wiring issues in Oxygen due to the mix -
> some of which now apparently having propagated to Neon, as seen in the
> thread linked to by Ed. I'm very much in doubt that even using a fixed
> httpclient 4.5 bundle would solve these...
> 
> Best,
> Carsten
> 
> [1] https://pastebin.com/Guu7G3ub
> [2] https://pastebin.com/gjkGrR0g
> 
> > -Original Message-
> > From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-
> > issues-dev-boun...@eclipse.org] On Behalf Of Jeff Johnston
> > Sent: Thursday, March 30, 2017 5:58 PM
> > To: Cross project issues 
> > Subject: Re: [cross-project-issues-dev] Neon.3 Update Problems
> > 
> > Regarding the Linux Tools issue.  This was due to the Oxygen M4 orbit repo
> > referenced
> > as part of a patch that upgraded the level of docker-client.
> > 
> > I will cut a 5.3.1 release of Linux Tools today using the Orbit M6 repo.
> > Can this be
> > aggregated or used to patch the issue?
> > 
> > -- Jeff J.
> > 
> > - Original Message -
> > >
> > >
> > > Hi,
> > >
> > > I'm concerned about the number of problems I see regarding updates to
> > Neon.3.
> > > For example, the missing MPC problem:
> > >
> > >
> > https://www.eclipse.org/forums/index.php/mv/msg/1085206/1758538/#msg_17585
> > 38
> > >
> > > It looks just like the problem we've been having with Oxygen M5/M6. That
> > > problem I believe traces back to a broken version of httpclient that
> > worked
> > > its way into Oxygen M5:
> > >
> > >
> > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=511333
> > >
> > >
> > > Rather than immediately fixing the problem and fixing M5, the problem
> > was
> > > allowed to propagate; weird and bizarre things were done to modify
> > > downstream code to explicitly exclude the broken version:
> > >
> > >
> > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=511406
> > >
> > > Of course such upper bound constraints also explicitly exclude the new
> > fixed
> > > version when it came along, so now it seems M6 is also broken, because
> > of
> > > wiring issues:
> > >
> > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=513809
> > >
> > > I think the wiring issues arose to a large extent because of the things
> > done
> > > during M5. In my opinion what should have happened in M5 is that the
> > Orbit
> > > bundle was immediately fixed (or reverted to the older version) and M5
> > was
> > > respun to ensure that no broken version of httpclient ever propagated
> > > further into the echo system. The last thing I would ever have expected
> > (and
> > > I personally would have refused to do) is for downstream clients to make
> > > changes to explicitly exclude a broken version. Please let's never do
> > that
> > > again. And please let's never behave as if the Eclipse Platform
> > project's
> > > build can't be respun to fix problem. Surely we can't have a policy in
> > place
> > > where no matter the state of the platform's build, it must remain as is,
> > > broken Orbit bundles and all.
> > >
> > >
> > > But what seems even worse, though I don't fully understand the problem,
> > is
> > > how this broken orbit bundle id='org.apache.httpcomponents.httpclient'
> > > version='

Re: [cross-project-issues-dev] Neon.3 Update Problems

[Jeff Johnston]

Regarding the Linux Tools issue.  This was due to the Oxygen M4 orbit repo 
referenced
as part of a patch that upgraded the level of docker-client.

I will cut a 5.3.1 release of Linux Tools today using the Orbit M6 repo.  Can 
this be
aggregated or used to patch the issue?

-- Jeff J.

- Original Message -
> 
> 
> Hi,
> 
> I'm concerned about the number of problems I see regarding updates to Neon.3.
> For example, the missing MPC problem:
> 
> https://www.eclipse.org/forums/index.php/mv/msg/1085206/1758538/#msg_1758538
> 
> It looks just like the problem we've been having with Oxygen M5/M6. That
> problem I believe traces back to a broken version of httpclient that worked
> its way into Oxygen M5:
> 
> 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=511333
> 
> 
> Rather than immediately fixing the problem and fixing M5, the problem was
> allowed to propagate; weird and bizarre things were done to modify
> downstream code to explicitly exclude the broken version:
> 
> 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=511406
> 
> Of course such upper bound constraints also explicitly exclude the new fixed
> version when it came along, so now it seems M6 is also broken, because of
> wiring issues:
> 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=513809
> 
> I think the wiring issues arose to a large extent because of the things done
> during M5. In my opinion what should have happened in M5 is that the Orbit
> bundle was immediately fixed (or reverted to the older version) and M5 was
> respun to ensure that no broken version of httpclient ever propagated
> further into the echo system. The last thing I would ever have expected (and
> I personally would have refused to do) is for downstream clients to make
> changes to explicitly exclude a broken version. Please let's never do that
> again. And please let's never behave as if the Eclipse Platform project's
> build can't be respun to fix problem. Surely we can't have a policy in place
> where no matter the state of the platform's build, it must remain as is,
> broken Orbit bundles and all.
> 
> 
> But what seems even worse, though I don't fully understand the problem, is
> how this broken orbit bundle id='org.apache.httpcomponents.httpclient'
> version='4.5.2.v20161115-1643' got into the Neon release train repository.
> Given all the problems it caused in Oxygen M5 surely we should have avoided
> that at all costs. I suspect it came from this repository:
> 
> 
> http://download.eclipse.org/linuxtools/update-neon-docker
> 
> I say that because that repo contains the broken version of httpclient and
> the versions of the docker IUs in that repo are the same as the versions in
> the neon release train, so it seems to me the bundles from this repo were
> aggregated into Neon.
> 
> So now the problems we have in Oxygen M5 and M6 are also problems for the
> users of Neon.3. That makes me very sad. Users expect update releases to be
> stable. Surely we're doing something very wrong to get into a state where a
> bundle known to be problematic nevertheless works its way into the final
> stable update of the Neon...
> 
> I don't know if the EGit update problems are at all related:
> 
> https://www.eclipse.org/forums/index.php/mv/msg/1085206/1758538/#msg_1758538
> 
> It definitely looks like a different problem, but
> org.slf4j.api_1.7.10.v20160921-1923 also comes from the update-neon-docker
> update site. And that's not a version that's in
> http://download.eclipse.org/tools/orbit/downloads/latest-R , i.e., it
> appears not to be a released version. So again, one has to wonder how this
> worked its way into Neon.3 causing update problems for Neon.3...
> 
> 
> Regards,
> Ed
> 
> ___
> 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 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] Requesting an extension past 5:00 pm for Linux Tools RC4a contribution

[Jeff Johnston]

Linux Tools is requesting an extension past 5:00 pm for our RC4 contribution.

We already submitted something yesterday, but we have solved a fairly major
bug which can freeze the docker daemon and are being delayed by gerrit (one
of our tests sometimes freezes).  The patch has already gone through our
master repo, but hasn't cleared for our stable-5.2 repo which is used to
build Neon.2.

I don't anticipate any issues but the time deadline.

-- Jeff J.
___
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] Upgrading HIPPs to SLES12 (Part 2)

[Jeff Johnston]

Linux Tools has an issue.  Please delay this until any day after Wednesday.  
That is our deadline (+3 project)
for Neon.1 RC4 (final build).  I don't want to compound any last minute 
problems we are trying to
fix by figuring out why the build system is not working or tests are showing 
new failures.

-- Jeff J. (Linux Tools) 

- Original Message -
> Hi,
> 
> The following HIPPs will be upgraded to SLES12:
> 
> * andmore
> * ecf
> * eclipsescada
> * efxclipse
> * egit
> * gyrex
> * hudson
> * linuxtools
> * orion
> * osee
> * recommenders
> * sapphire
> * swtbot
> 
> The upgrade is scheduled for Wednesday, September 14th, 10am EDT.
> 
> Downtime will be a few hours.
> 
> 
> Please let me know if you have any concerns.
> 
> Regards,
> 
> Fred
> ___
> 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 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] Gerrit is failing to connect to https://hudson.eclipse.org

[Jeff Johnston]

I hit the restart button on the account page and it appeared to bring down
the hipp instance as I had to wait a bit for it to come up.  I will try your
suggestion, but for the time-being I have cheated and put the launchbar stuff
in the Linux Tools download area as a temporary work-around.

-- Jeff J.

- Original Message -
> On 08/30/2016 05:32 PM, Jeff Johnston wrote:
> 
> 
> I tried restarting our hipp instance and now linuxtools hudson pages are
> unavailable (503). This is bad
> timing since we are trying to get RC2 out for tomorrow.
> While I don't know if "restarting" will fix the issue, just thought I would
> mention that I have not seen "restart" work for a very long time.
> (Even though it "acts like" it does on the account page.)
> 
> But what does work, for me, is to "stop" the server. And, then "start" it.
> [Not sure if you meant "restart" literally or not or if this is common
> knowledge.]
> 
> HTH
> 
> ___
> 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 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] Gerrit is failing to connect to https://hudson.eclipse.org

[Jeff Johnston]

I tried restarting our hipp instance and now linuxtools hudson pages are 
unavailable (503).  This is bad
timing since we are trying to get RC2 out for tomorrow.

- Original Message -
> I am having trouble with the Linux Tools gerrit jobs.  We get the launchbar
> stuff from
> the hudson launchbar-master job last successful build.
> 
> I keep getting no route to host when our target file tries to connect to the
> repo.
> 
> Any ideas?
> 
> -- Jeff J.
> ___
> 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 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] Gerrit is failing to connect to https://hudson.eclipse.org

[Jeff Johnston]

I am having trouble with the Linux Tools gerrit jobs.  We get the launchbar 
stuff from
the hudson launchbar-master job last successful build.

I keep getting no route to host when our target file tries to connect to the 
repo.

Any ideas?

-- Jeff J.
___
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] LDT repo doesn't exist for Neon_maintenance

[Jeff Johnston]

The ldt repo specified in ldt.b3aggricon for the Neon_maintenance release 
specifies
http://download.eclipse.org/ldt/releases/milestones/1.4M3 which doesn't 
currently exist.

It appears possibly that an ldt aggregation has wiped out the milestones 
directory as the
composites have no children.

I have modified it temporarily to releases/stable/1.4 so that the aggregation 
would
validate locally and pass for gerrit.  I have cc'd all the ldt maintainers 
listed above.

Could one of the LDT folks fix this if necessary to a milestone release or else 
confirm
that it should be as I have modified it?

Thanks,

-- Jeff J.
___
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] Linux Tools will participate in Oxygen with major release 6.0.0 and offset +3

[Jeff Johnston]

This is to confirm that the Linux Tools project will participate in the Oxygen 
release
and plans to provide major release 6.0.0 with offset +3.

The release plan has been created: 

https://projects.eclipse.org/projects/tools.linuxtools/releases/6.0.0

with details to follow regarding planned changes.

-- Jeff J.
___
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] Hudson appears to be down

[Jeff Johnston]

Thanks.

-- Jeff J.

- Original Message -
> Looks like it's the linuxtools instance.  Just go restart it at
> http://dev.eclipse.org/site_login (using the HIPP Control).
> 
> Denis
> 
> 
> On 24/05/16 04:05 PM, Jeff Johnston wrote:
> > Anyone else having Hudons problems?  Our Linux Tools Hudson instance cannot
> > be reached.  Error 503 Service Unavailable
> >
> > -- Jeff J.
> > ___
> > 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 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 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] Hudson appears to be down

[Jeff Johnston]

Anyone else having Hudons problems?  Our Linux Tools Hudson instance cannot
be reached.  Error 503 Service Unavailable

-- Jeff J.
___
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] Linux Tools will participate in Neon

[Jeff Johnston]

This is to confirm that Linux Tools will participate in Neon with major release 
5.0.0 and offset +3.

-- Jeff Johnston (Linux Tools Project)
___
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] Linux Tools RC3 just needs to finish gerrit validation

[Jeff Johnston]

Ok, gerrit review finished and b3aggrcon is merged to Mars_Maintenance.

Thanks,

-- Jeff J.

- Original Message -
> We are just waiting for gerrit validation to push our Mars.1 RC3 build.
> 
> -- Jeff J.
> ___
> 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 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] Linux Tools RC3 just needs to finish gerrit validation

[Jeff Johnston]

We are just waiting for gerrit validation to push our Mars.1 RC3 build.

-- Jeff J.
___
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] Can we have a slight extension this evening ... plus ...

[Jeff Johnston]

Hi David,

We are done.  I also fixed the MPC contribution error at the same time as it 
was obvious.

Thanks,

-- Jeff J.

- Original Message -
> Yes, that's fine.
> 
> Plus, I see some other problems:
> 
> 1) Being a good citizen, I added "time out if build is stuck" recently, but
> see I was too optimistic on some of the times (and one was a typo). I have
> increased the time limits.
> 2) MPC contribution for Mars.1 RC2 is currently causing Mars build to fail. I
> mention it here, since I have not gotten "blame mail" for it yet, so
> originator may not have either?
> 3) The Neon VALIDATE.gerrit job failed with a very unusual error, so I
> "cleaned workspace" and re-triggered the build. It ran ok then, so not sure
> what caused original issue?
> 
> Thanks,
> 
> 
> 
> 
> From: Jeff Johnston 
> To: Cross project issues ,
> Date: 09/02/2015 03:39 PM
> Subject: [cross-project-issues-dev] Can we have a slight extension this
> evening
> Sent by: cross-project-issues-dev-boun...@eclipse.org
> 
> 
> 
> 
> Linux Tools is trying to get our RC2 build finished, but it might be tight
> before 5:00 pm.
> 
> Can we have a slight time extension please? We expect to have it finished.
> 
> Thanks,
> 
> -- Jeff J.
> ___
> 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 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 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] Can we have a slight extension this evening

[Jeff Johnston]

Linux Tools is trying to get our RC2 build finished, but it might be tight 
before 5:00 pm.

Can we have a slight time extension please?  We expect to have it finished.

Thanks,

-- Jeff J.
___
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] Linux Tools participation in Neon

[Jeff Johnston]

Sorry.  I should have said 4.3.0 minor release below.

- Original Message -
> This is to indicate that Linux Tools intends to participate in the Neon
> rekease with
> its 4.1.0 minor release.  The offset will remain at +3
> 
> -- Jeff J.
> 
> ___
> 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 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] Linux Tools participation in Neon

[Jeff Johnston]

This is to indicate that Linux Tools intends to participate in the Neon rekease 
with
its 4.1.0 minor release.  The offset will remain at +3

-- Jeff J.

___
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] Gerrit for org.simrel.build keeps asking me to rebase my change

[Jeff Johnston]

Adding the change-id seems to have worked.  My patch is now merged to master.

-- Jeff J.

- Original Message -
> I did use the rebase button (twice in fact).  My change has nothing to do
> with any
> other files.  I then tried rebasing locally on my system and resubmitting.
> That got
> me into the mess with two changes out there.  I have since added the
> change-id, abandoned
> the duplicate job, and restarted the build.
> 
> It validated locally.
> 
> -- Jeff J.
> 
> - Original Message -
> > By "release", you mean you press the submit button?
> > 
> > Could it be asking you to "rebase" your commit? (Which, normally can be
> > done
> > with the "rebase" button.?
> > 
> > 
> > 
> > 
> > From: Jeff Johnston 
> > To: Cross project issues ,
> > Date: 06/10/2015 03:31 PM
> > Subject: [cross-project-issues-dev] Gerrit for org.simrel.build keeps
> > asking
> > me to rebase my change
> > Sent by: cross-project-issues-dev-boun...@eclipse.org
> > 
> > 
> > 
> > 
> > Hello,
> > 
> > I'm trying to get the RC4 change in for Linux Tools. I keep getting a
> > successful
> > build, then after I review it, it says I have to rebase my change. I do so,
> > it rebuilds
> > successfully and then claims I need to rebase it again. I am only changing
> > the
> > linuxtools.b3aggrcon file.
> > 
> > Is anyone else experiencing this issue?
> > 
> > -- Jeff J.
> > ___
> > 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 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 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 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] Gerrit for org.simrel.build keeps asking me to rebase my change

[Jeff Johnston]

I did use the rebase button (twice in fact).  My change has nothing to do with 
any
other files.  I then tried rebasing locally on my system and resubmitting.  
That got
me into the mess with two changes out there.  I have since added the change-id, 
abandoned
the duplicate job, and restarted the build.

It validated locally.

-- Jeff J.

- Original Message -
> By "release", you mean you press the submit button?
> 
> Could it be asking you to "rebase" your commit? (Which, normally can be done
> with the "rebase" button.?
> 
> 
> 
> 
> From: Jeff Johnston 
> To: Cross project issues ,
> Date: 06/10/2015 03:31 PM
> Subject: [cross-project-issues-dev] Gerrit for org.simrel.build keeps asking
> me to rebase my change
> Sent by: cross-project-issues-dev-boun...@eclipse.org
> 
> 
> 
> 
> Hello,
> 
> I'm trying to get the RC4 change in for Linux Tools. I keep getting a
> successful
> build, then after I review it, it says I have to rebase my change. I do so,
> it rebuilds
> successfully and then claims I need to rebase it again. I am only changing
> the
> linuxtools.b3aggrcon file.
> 
> Is anyone else experiencing this issue?
> 
> -- Jeff J.
> ___
> 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 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 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] Gerrit for org.simrel.build keeps asking me to rebase my change

[Jeff Johnston]

Thanks,

That job was after the issues occurred.  I tried locally rebasing and 
resubmitting and that
created a separate gerrit review (because no change-id).  I then added the 
changeid and it added to the
original gerrit review.  I have just abandoned the non-change-id version and am
rebuilding the 4th patch set.  This definitely is more difficult than it should 
be.  I don't
have these issues with our gerrit validator for Linux Tools.

-- Jeff J.

- Original Message -
> At the moment there seem to be two competing changes in Gerrit:
> 
> [1] https://git.eclipse.org/r/#/c/49960/1
> [2] https://git.eclipse.org/r/#/c/49957/4
> 
> Both of them have the same parent commit, but only [2] has a change ID that
> allows Gerrit to assign updated patch sets to the same change. Maybe this
> causes some trouble, too, at least it does not help. I'd suggest to abandon
> [1].
> 
> Regards,
> Markus
> 
> 
> On 10 June 2015 at 21:36, Eike Stepper < step...@esc-net.de > wrote:
> 
> 
> Am 10.06.2015 um 21:30 schrieb Jeff Johnston:
> 
> 
> Hello,
> 
> I'm trying to get the RC4 change in for Linux Tools. I keep getting a
> successful
> build, then after I review it, it says I have to rebase my change. I do so,
> it rebuilds
> successfully and then claims I need to rebase it again. I am only changing
> the
> linuxtools.b3aggrcon file.
> 
> Is anyone else experiencing this issue?
> One night I had the same problem. I worked around it by rebasing and setting
> it to verified +1 myself. Then I could immediately submit it.
> 
> Cheers
> /Eike
> 
> 
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
> 
> 
> 
> 
> ___
> 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 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 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] Gerrit for org.simrel.build keeps asking me to rebase my change

[Jeff Johnston]

Hello,

I'm trying to get the RC4 change in for Linux Tools.  I keep getting a 
successful
build, then after I review it, it says I have to rebase my change.  I do so, it 
rebuilds
successfully and then claims I need to rebase it again.  I am only changing the
linuxtools.b3aggrcon file.

Is anyone else experiencing this issue?

-- Jeff J.
___
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] Almost all projects are ready for the June 10 release review

[Jeff Johnston]

Hi Wayne,

Could the Linux Tools release review also be scheduled for June 10th?  We 
originally
scheduled it for the 11th which doesn't line up.

-- Jeff J.

- Original Message -
> It was an oversight. My apologies. Thanks for looking.
> 
> Wayne
> 
> On 08/06/15 05:03 AM, Goulwen Le Fur wrote:
> 
> 
> 
> Hi Wayne,
> 
> I think that everything is ok for the EEF project (modeling.emtf.eef),
> but It doesn't appear in the list of June 10 reviews. Given that it
> isn't included in your two bugzilla queries, can you tell me if you miss
> something from this project or if everything is ok for you.
> 
> Thks,
> 
> --
> Wayne Beaton
> @waynebeaton
> The Eclipse Foundation
> 
> ___
> 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 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] Trying to submit a change to simrel and no gerrit validation

[Jeff Johnston]

That did it, thanks.

-- Jeff J.

- Original Message -
> Ok ... thanks for the detail. I suspect I did make a (perfectly logical :)
> change that Gerrit doesn't quite know how to interpret. :/
> 
> I have "changed it back" ... and I don't see a build starting right away ..
> so, my apologies, but can you try "touching" your patch set (or, what ever
> the right terminology is) and we'll see if it now works after my "revert" in
> the configuration.
> 
> Thanks,
> 
> 
> 
> 
> From: Jeff Johnston 
> To: Cross project issues ,
> Date: 06/05/2015 01:19 PM
> Subject: Re: [cross-project-issues-dev] Trying to submit a change to simrel
> and no gerrit validation
> Sent by: cross-project-issues-dev-boun...@eclipse.org
> 
> 
> 
> 
> I made a commit for master on org.eclipse.simrel.build. I then pushed
> to gerrit as I always do by pushing to: my remote in .git/config:
> 
> [remote "review"]
> url =
> ssh://jjohns...@git.eclipse.org:29418/simrel/org.eclipse.simrel.build.git
> push = HEAD:refs/for/master
> 
> This creates a gerrit review:
> 
> https://git.eclipse.org/r/#/c/49543/
> 
> but it did not start the validate job. I tried retriggering by changing the
> commit log
> and again, no validate. I even tried adding Hudson CI as a reviewer which was
> a last
> attempt hack. Again, no build started.
> 
> I just changed my password as I was getting warning messages from Eclipse,
> but I wouldn't
> think that would affect ssh access.
> 
> -- Jeff J.
> 
> - Original Message -
> > Should work. But let's go over basics.
> > 
> > When you say your "project's Gerrit validator" do you mean the Sim Rel job
> > called
> > simrel.mars.runaggregator.VALIDATE.gerrit
> > I don't think so, since it has not ran at all for 18 hours, but, just in
> > case
> > you do, you still need to "submit" a change to put
> > the change into the master branch.
> > 
> > Second, did you actually change a file in the org.eclipse.simrel.build Git
> > repository?
> > If so, I don't see it in the log, but that (changing something in master)
> > is
> > what "triggers" the simrel.mars.runaggregator.VALIDATE job.
> > 
> > It does does not run periodically, and it does not run based on changes in
> > project's repositories.
> > 
> > If you mean you have a change in your project repository, you can either
> > change your b3aggrcon file, or, you can
> > (after logging in to that Hudson instance) use the web interface to start
> > your own build in simrel.mars.runaggregator.VALIDATE.
> > 
> > Hudson checks every 15 minutes if there has been a change to files in
> > o.e.simrel.build.
> > 
> > Hope that clears it up (if not, please ask again).
> > 
> > 
> > 
> > 
> > 
> > 
> > From: Jeff Johnston 
> > To: Cross project issues ,
> > Date: 06/04/2015 07:56 PM
> > Subject: [cross-project-issues-dev] Trying to submit a change to simrel and
> > no gerrit validation
> > Sent by: cross-project-issues-dev-boun...@eclipse.org
> > 
> > 
> > 
> > 
> > I'm trying to submit a change to org.eclipse.simrel.build in preparation
> > for RC4, but the validator build isn't starting. Is there some reason for
> > this? My project's gerrit validator is working fine.
> > 
> > -- Jeff J.
> > ___
> > 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 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 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 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 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] Trying to submit a change to simrel and no gerrit validation

[Jeff Johnston]

I made a commit for master on org.eclipse.simrel.build.  I then pushed
to gerrit as I always do by pushing to: my remote in .git/config:

[remote "review"]
url = 
ssh://jjohns...@git.eclipse.org:29418/simrel/org.eclipse.simrel.build.git
push = HEAD:refs/for/master

This creates a gerrit review:

https://git.eclipse.org/r/#/c/49543/

but it did not start the validate job.  I tried retriggering by changing the 
commit log
and again, no validate.  I even tried adding Hudson CI as a reviewer which was 
a last
attempt hack.  Again, no build started.

I just changed my password as I was getting warning messages from Eclipse, but 
I wouldn't
think that would affect ssh access.

-- Jeff J.

- Original Message -
> Should work. But let's go over basics.
> 
> When you say your "project's Gerrit validator" do you mean the Sim Rel job
> called
> simrel.mars.runaggregator.VALIDATE.gerrit
> I don't think so, since it has not ran at all for 18 hours, but, just in case
> you do, you still need to "submit" a change to put
> the change into the master branch.
> 
> Second, did you actually change a file in the org.eclipse.simrel.build Git
> repository?
> If so, I don't see it in the log, but that (changing something in master) is
> what "triggers" the simrel.mars.runaggregator.VALIDATE job.
> 
> It does does not run periodically, and it does not run based on changes in
> project's repositories.
> 
> If you mean you have a change in your project repository, you can either
> change your b3aggrcon file, or, you can
> (after logging in to that Hudson instance) use the web interface to start
> your own build in simrel.mars.runaggregator.VALIDATE.
> 
> Hudson checks every 15 minutes if there has been a change to files in
> o.e.simrel.build.
> 
> Hope that clears it up (if not, please ask again).
> 
> 
> 
> 
> 
> 
> From: Jeff Johnston 
> To: Cross project issues ,
> Date: 06/04/2015 07:56 PM
> Subject: [cross-project-issues-dev] Trying to submit a change to simrel and
> no gerrit validation
> Sent by: cross-project-issues-dev-boun...@eclipse.org
> 
> 
> 
> 
> I'm trying to submit a change to org.eclipse.simrel.build in preparation
> for RC4, but the validator build isn't starting. Is there some reason for
> this? My project's gerrit validator is working fine.
> 
> -- Jeff J.
> ___
> 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 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 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] Trying to submit a change to simrel and no gerrit validation

[Jeff Johnston]

I'm trying to submit a change to org.eclipse.simrel.build in preparation
for RC4, but the validator build isn't starting.  Is there some reason for
this?  My project's gerrit validator is working fine.

-- Jeff J.
___
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] Linux Tools participation in Mars

[Jeff Johnston]

Changing the subject line as we still don't appear on the list and others have
since submitted their intention and been added.  Perhaps, replying to the other
subject line made it hard to see.  Details below.

-- Jeff J.

- Original Message -
From: "Jeff Johnston" 
To: "Cross project issues" 
Sent: Thursday, December 4, 2014 1:07:15 PM
Subject: Re: [cross-project-issues-dev] Are *you* ready for M4?

Ok, thanks for the info.

Let this be Linux Tools statement of intent to participate in Mars.

We will be releasing Linux Tools 4.0 (major release) which has a release record 
at:

https://projects.eclipse.org/projects/tools.linuxtools/releases/4.0.0

Our offset as always is +3

-- Jeff J.

- Original Message -
From: "Wayne Beaton" 
To: cross-project-issues-dev@eclipse.org
Sent: Thursday, December 4, 2014 12:52:16 PM
Subject: Re: [cross-project-issues-dev] Are *you* ready for M4?

I need a little more information. 

https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early_.28M4.29
 

FWIW, I made it is a requirement to formally announce your intent to 
participate because we have had too many cases in the past where we've 
automatically just rolled over from one year to the next and the project teams 
forgot to engage, resulting in last minute scrambles. 

I wish that I had the bandwidth to just automatically include those projects 
who are obviously paying attention (e.g. CDT), but I don't. 

I can probably figure out the release based on the project metadata, but it's 
way easier for me if you tell me which release you're including. I also need to 
know the offset. Again, I can figure this out, but it takes at least some 
(albeit trivial) effort that adds up. Besides, the offset information is 
something that other participants care about, so it's nice to let people know 
in the public forum. 

An explicit declaration of participation each year helps me and everybody else 
know that the project is still engaged. 

HTH, 

Wayne 

On 04/12/14 12:34 PM, Jeff Johnston wrote: 



I didn't know we still had to declare intent.  I thought it was implied by our 
enablement in b3aggrcon file.

Anyway, Linux Tools will be participating in Mars.

-- Jeff J.

- Original Message -
From: "David M Williams"  To: 
cross-project-issues-dev@eclipse.org Sent: Wednesday, December 3, 2014 9:05:58 
PM
Subject: [cross-project-issues-dev] Are *you* ready for M4?

I wanted to remind everyone that M4 is not that far off. 

In part, because this is the milestone we switch to a "one week window". M4 +0 
is 12/12 and +3 is 12/17. For that reason, it is good to make an early 
"warm-up" contributions that is near final, even if your final contribution is 
later made on your "latest possible" +n day. 

Plus, three projects still have disabled features or repositories: 
mft.b3aggrcon - org.eclipse.simrel.build (2 matches) 
mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build 
soa-bpmn2-modeler.b3aggrcon - org.eclipse.simrel.build 

PLUS ... have you declared your intent? Or, lack of intent? (I know one or two 
have) but, according to the "who is participating" web page, at 
https://projects.eclipse.org/releases/mars there are 21 projects that have 
"dropped out" of Mars! (That list is about half way down the left-most column.) 
I am pretty sure some of them do not intend to drop out (such as CDT! WTP! 
Xpand!? Mylyn! ... ) and I am moderately sure some of those have declared 
intent on this list, so I am wondering if there is a problem with your "release 
record" ... or something? In any case, please work with Wayne if something is 
amiss or missed. And, it is helpful and polite that if you have been a long 
term participant, and now decided to no longer participate, to say so 
explicitly ... to us on this list, not to mention your adopters via your 
dev-lists, etc. I mention this now, since at some point, those who show up on 
the "will not participate list" will have their files removed from the 
aggregator and t!
 he reposi
 tory, for the simple reason of giving a realistic view of "what is coming" to 
users, adopters, and other projects. 

Greatest thanks to all, 


___
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 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 

-- 
Wayne Beaton 
@waynebeaton 
The Eclipse Foundation 

Re: [cross-project-issues-dev] Are *you* ready for M4?

[Jeff Johnston]

Ok, thanks for the info.

Let this be Linux Tools statement of intent to participate in Mars.

We will be releasing Linux Tools 4.0 (major release) which has a release record 
at:

https://projects.eclipse.org/projects/tools.linuxtools/releases/4.0.0

Our offset as always is +3

-- Jeff J.

- Original Message -
From: "Wayne Beaton" 
To: cross-project-issues-dev@eclipse.org
Sent: Thursday, December 4, 2014 12:52:16 PM
Subject: Re: [cross-project-issues-dev] Are *you* ready for M4?

I need a little more information. 

https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early_.28M4.29
 

FWIW, I made it is a requirement to formally announce your intent to 
participate because we have had too many cases in the past where we've 
automatically just rolled over from one year to the next and the project teams 
forgot to engage, resulting in last minute scrambles. 

I wish that I had the bandwidth to just automatically include those projects 
who are obviously paying attention (e.g. CDT), but I don't. 

I can probably figure out the release based on the project metadata, but it's 
way easier for me if you tell me which release you're including. I also need to 
know the offset. Again, I can figure this out, but it takes at least some 
(albeit trivial) effort that adds up. Besides, the offset information is 
something that other participants care about, so it's nice to let people know 
in the public forum. 

An explicit declaration of participation each year helps me and everybody else 
know that the project is still engaged. 

HTH, 

Wayne 

On 04/12/14 12:34 PM, Jeff Johnston wrote: 



I didn't know we still had to declare intent.  I thought it was implied by our 
enablement in b3aggrcon file.

Anyway, Linux Tools will be participating in Mars.

-- Jeff J.

- Original Message -
From: "David M Williams"  To: 
cross-project-issues-dev@eclipse.org Sent: Wednesday, December 3, 2014 9:05:58 
PM
Subject: [cross-project-issues-dev] Are *you* ready for M4?

I wanted to remind everyone that M4 is not that far off. 

In part, because this is the milestone we switch to a "one week window". M4 +0 
is 12/12 and +3 is 12/17. For that reason, it is good to make an early 
"warm-up" contributions that is near final, even if your final contribution is 
later made on your "latest possible" +n day. 

Plus, three projects still have disabled features or repositories: 
mft.b3aggrcon - org.eclipse.simrel.build (2 matches) 
mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build 
soa-bpmn2-modeler.b3aggrcon - org.eclipse.simrel.build 

PLUS ... have you declared your intent? Or, lack of intent? (I know one or two 
have) but, according to the "who is participating" web page, at 
https://projects.eclipse.org/releases/mars there are 21 projects that have 
"dropped out" of Mars! (That list is about half way down the left-most column.) 
I am pretty sure some of them do not intend to drop out (such as CDT! WTP! 
Xpand!? Mylyn! ... ) and I am moderately sure some of those have declared 
intent on this list, so I am wondering if there is a problem with your "release 
record" ... or something? In any case, please work with Wayne if something is 
amiss or missed. And, it is helpful and polite that if you have been a long 
term participant, and now decided to no longer participate, to say so 
explicitly ... to us on this list, not to mention your adopters via your 
dev-lists, etc. I mention this now, since at some point, those who show up on 
the "will not participate list" will have their files removed from the 
aggregator and the reposi
 tory, for the simple reason of giving a realistic view of "what is coming" to 
users, adopters, and other projects. 

Greatest thanks to all, 


___
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 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 

-- 
Wayne Beaton 
@waynebeaton 
The Eclipse Foundation 

___
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 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] Are *you* ready for M4?

[Jeff Johnston]

I didn't know we still had to declare intent.  I thought it was implied by our 
enablement in b3aggrcon file.

Anyway, Linux Tools will be participating in Mars.

-- Jeff J.

- Original Message -
From: "David M Williams" 
To: cross-project-issues-dev@eclipse.org
Sent: Wednesday, December 3, 2014 9:05:58 PM
Subject: [cross-project-issues-dev] Are *you* ready for M4?

I wanted to remind everyone that M4 is not that far off. 

In part, because this is the milestone we switch to a "one week window". M4 +0 
is 12/12 and +3 is 12/17. For that reason, it is good to make an early 
"warm-up" contributions that is near final, even if your final contribution is 
later made on your "latest possible" +n day. 

Plus, three projects still have disabled features or repositories: 
mft.b3aggrcon - org.eclipse.simrel.build (2 matches) 
mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build 
soa-bpmn2-modeler.b3aggrcon - org.eclipse.simrel.build 

PLUS ... have you declared your intent? Or, lack of intent? (I know one or two 
have) but, according to the "who is participating" web page, at 

https://projects.eclipse.org/releases/mars 

there are 21 projects that have "dropped out" of Mars! (That list is about half 
way down the left-most column.) I am pretty sure some of them do not intend to 
drop out (such as CDT! WTP! Xpand!? Mylyn! ... ) and I am moderately sure some 
of those have declared intent on this list, so I am wondering if there is a 
problem with your "release record" ... or something? In any case, please work 
with Wayne if something is amiss or missed. And, it is helpful and polite that 
if you have been a long term participant, and now decided to no longer 
participate, to say so explicitly ... to us on this list, not to mention your 
adopters via your dev-lists, etc. I mention this now, since at some point, 
those who show up on the "will not participate list" will have their files 
removed from the aggregator and the repository, for the simple reason of giving 
a realistic view of "what is coming" to users, adopters, and other projects. 

Greatest thanks to all, 


___
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 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] Reminder today is last build for Luna SR1 ... and Mars M2 is close!

[Jeff Johnston]

Not sure how we missed that about.html file, but I have just updated the Linux 
Tools RC4
offering to fix our problem.

-- Jeff J.

- Original Message -
> From: "David M Williams" 
> To: cross-project-issues-dev@eclipse.org
> Sent: Wednesday, September 17, 2014 10:08:16 AM
> Subject: [cross-project-issues-dev] Reminder today is last build for Luna 
> SR1 ... and Mars M2 is close!
> 
> I'm sure every one knows already, but today (5 PM Eastern, or so) is last
> aggregation build for Luna SR1 ... then EPP packages will be built ... and
> next week is "quiet week" ... where the idea is everyone can prepare for the
> release, update "info center" if needed, do even more testing, especially
> adopters who want to have their release ready the same time as we do ...
> etc. One thing to test well is "update", that's always a nasty failure to
> discover after we have released. For "how to do" see
> 
> https://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#What.27s_the_best_way_to_test_with_the_staging_repository.3F
> 
> The other thing that's good to check is that the version you think you are
> contributing, is what actually ends up in the 'maintenance' repo ... and
> that p2 (and other constraints) don't cause something higher or lower to be
> picked. Sometimes this "multiple versions" repo report is helpful for quick
> sanity check (but, nothing beats "manually" checking what is installed from
> Sim. Release, compared to what is installed from your own repo.
> http://build.eclipse.org/simrel/luna/reporeports/reports/nonUniqueVersions.txt
> 
> As far as I know, Luna is looking well (everyone is "enabled"), but there are
> more "errors" in the fundamentals of "repo report" than I'd like to see. I
> really don't understand why "about files" and "unsigned bundles" are not
> correct in every contribution? I guess it depends on your releng processes?
> 
> http://build.eclipse.org/simrel/luna/reporeports/
> 
> If anyone anticipates problems or has any questions, do let us know earlier
> rather than later!
> 
> 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
___
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] Linux Tools last minute update for RC3

[Jeff Johnston]

Hello,

There was a request to update our RC3 offering as there were a few LTTng changes
not included in our initial RC3 aggregation.  I have updated the b3aggrcon
file and pushed to Luna_Maintenance.  If the deadline has passed, so be it, the 
changes
will be part of RC4, otherwise, please include it so we can do more extensive 
RC3 testing.

Thanks,

-- Jeff J. 
___
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] Kepler SR2 aggregation is failing

[Jeff Johnston]

I have made a patch to the m2t-acceleo.b3aggrcon file.  The repo mentioned 
below has disappeared,
but I found 
file:///home/data/httpd/download.eclipse.org/acceleo/updates/milestones/3.4/S201401221203

Changing the repo to the location above, the aggregation validates.  If someone 
comes
along and feels that is the wrong solution, feel free to correct.

-- Jeff J.

- Original Message -
From: "Michael Golubev" 
To: "Cross project issues" 
Sent: Wednesday, February 19, 2014 6:20:45 PM
Subject: [cross-project-issues-dev] Kepler SR2 aggregation is failing

Hello, 

For last couple of hours Keppler SR2 aggregator is failing [1] trying to find 
one of the repos: 

[exec] Unable to load repository file:///home/data/httpd/ 
download.eclipse.org/modeling/m2t/acceleo/updates/milestones/3.4/S201401221203 

To my understanding the last commits before the first failing build are not 
related to Acceleo contribution, so it rather means that the referenced 
location itself had been accidentally removed. 

Anyway we are now approaching the deadline and there are at least 2 
contributions (Mylyn and GMF-Tooling) that can't be built right now. Can 
someone please advice on how to proceed from here? 

[1] 
https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/job/simrel.kepler.runaggregator/827/
 

Regards, 
Michael 


-- 

Michael "Borlander" Golubev 
Eclipse Committer (GMF, UML2Tools) 
at Montages Think Tank, Prague, Czech Republic 
1165/1 Dvorecka, 14700, Prague-4 Podoli 

tek: +420 602 483 463 


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Kepler SR2 RC3 aggregation fails

[Jeff Johnston]

I have a fix if it is ok for me to change some other group's
b3aggrcon file.  

The example feature has an extraneous -Ys at the end of the identifier.  I
looked at the update-site referred to and that -Ys shouldn't be there.  

Birt also added a new contact but didn't add that contact to the simrel.b3aggr
file so it doesn't validate for me locally using the b3aggrcon tools.
I also have a fix for that, assuming that ch...@actuate.com is Chezy Palani.

-- Jeff J.


- Original Message -
> From: "Beth Tibbitts" 
> To: "Cross project issues" 
> Sent: Wednesday, February 12, 2014 2:10:21 PM
> Subject: Re: [cross-project-issues-dev] Kepler SR2 RC3 aggregation fails
> 
> Any news on this?
> 
> ...Beth
> 
> Beth Tibbitts
> b...@tibweb.com
> 
> 
> On Wed, Feb 12, 2014 at 6:04 AM, Ken Lee < ken@bsiag.com > wrote:
> 
> 
> 
> 
> 
> Hi all,
> 
> 
> 
> I just noticed that the Kepler aggregation job [1] fails due to a missing
> feature of the BIRT project: org.eclipse.birt.example.feature.group.
> 
> The last commit was pushed by the BIRT project itself. Could anyone of them
> fix that?
> 
> 
> 
> Thanks in advance.
> 
> 
> 
> Ken
> 
> 
> 
> [1]
> https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/job/simrel.kepler.runaggregator/805/console
> 
> 
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 
> 
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Change in signing plug-in results in repository changes

[Jeff Johnston]

In Linux Tools, we have switched over to use the 
eclipse-jarsigner-plugin instead of eclipse-signing-maven-plugin.


We have noted that in past builds, we ended up getting a top-level 
META-INF directory with signing info for artifacts.jar when we used the 
old eclipse-signing-maven-plugin.


Is this an issue?  Does anything use this info to verify that 
artifacts.jar is not tampered with?


-- Jeff J.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Linux Tools Participation in Luna

[Jeff Johnston]

There isn't much to add at this point.  We know that there will be API 
breakage from the LTTng plug-ins so we need to do a major release.  Our 
planning meeting is happening soon and it will fill in more details for 
what goes into our 2.2 release and what goes into Luna.


The release plan as it is can be found at:

https://projects.eclipse.org/projects/tools.linuxtools/releases/3.0.0

-- Jeff J.

On 09/09/2013 02:40 PM, Wayne Beaton wrote:

Please include a description.

Thanks,

Wayne

On 09/09/2013 02:38 PM, Jeff Johnston wrote:

This is to announce that the Linux Tools project will be participating
in the Luna simultaneous release.  We will be including our 3.0
release and we are a +3 project.

-- Jeff J.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



--
Wayne Beaton
Director of Open Source Projects, The Eclipse Foundation
<http://www.eclipse.org>
Learn about Eclipse Projects <http://www.eclipse.org/projects>
EclipseCon Europe 2013 <http://www.eclipsecon.org/europe2013>


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Linux Tools Participation in Luna

[Jeff Johnston]

This is to announce that the Linux Tools project will be participating 
in the Luna simultaneous release.  We will be including our 3.0 release 
and we are a +3 project.


-- Jeff J.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Jeff Johnston]

With CDT enabled, I have enabled Linux Tools.

On 08/21/2013 10:49 AM, Doug Schaefer wrote:
I've re-enabled CDT. Sorry for wasting the time of the person who put 
enabled="false" into our file.


Doug.

From: Sergey Boyko >
Reply-To: Cross project issues >

Date: Wednesday, 21 August, 2013 10:18 AM
To: Cross project issues >

Subject: Re: [cross-project-issues-dev] Status and outlook for Luna M1

QVTo was re-enabled for Luna.

Cheers...
 Sergey


On Wed, Aug 21, 2013 at 8:00 AM, David M Williams 
mailto:david_willi...@us.ibm.com>> wrote:


Doesn't look good. I'll admit there is one day left, but so far 50
projects have not even enabled their "contribution" to Luna
(pasted below).



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Trying to aggregate source features using b3 aggregator editor

[Jeff Johnston]

Thanks David,

I think you nailed it.  We are using tycho-extras to generate the source 
features from the regular features.  It isn't propagating the filters.


Each generated source feature has an include of the regular feature in it.

-- Jeff J.

On 05/21/2013 09:37 PM, David M Williams wrote:

Off hand, I'd guess related to filters. I've not looked in detail, but
nothing obviously wrong with your file or repo. But ... for filters,
it's complicated to get them right "for everything" ... and sure you'd
want your source "filtered", or might not display in all standalone
"info servers" (not sure about that ... just saying, should be tested).
But, back to filters ...

Just to give an example,
Let's say
 org.eclipse.linuxtools.callgraph.feature.feature.group
installs in a aggregator just fine. That means it an all its bundles
have a "matching" set of features, say to limit installation on to linux
only platforms.

Now, if when your source is added
 org.eclipse.linuxtools.callgraph.feature.source.feature.group

It may report "can not find
org.eclipse.linuxtools.callgraph.feature.feature.group" but what it may
really mean (or, should say) is
"can not find [it] while trying to install [source.group] for windows".

So, that's just a thought ... make sure your "source features/bundles"
have all the same filters as your code (since ... your source requires
your code ... which is a bit odd anyway, but  maybe a separate issues).

HTH





From: Jeff Johnston 
To: Cross project issues ,
Date: 05/21/2013 02:53 PM
Subject: [cross-project-issues-dev] Trying to aggregate source features
using b3 aggregator editor
Sent by: cross-project-issues-dev-boun...@eclipse.org




I am trying to add the Linux Tools source features (without categories)
so end-users can install them if desired.

When I add these features to the linuxtools.b3aggrcon file, I am getting
an error trying to validate the aggregation.  The source features
require the normal features and the b3 aggregator editor is saying that
the feature is missing.

The missing feature in question is also in the b3aggrcon file (with
category) and is found when validating the repository.  If I remove the
source features, the aggregation validates fine.

Below is the actual message.  Is there something wrong with our repo or
is it a known issue with the b3 aggregator editor trying to have new
feature groups requiring other new feature groups?

I have attached the b3aggrcon file for reference.

-- Jeff J.

===

Cannot complete the install because one or more required items could not
be found.
Missing requirement: C/C++ Call Graph Visualization Developer Resources
1.1.0.201305211237
(org.eclipse.linuxtools.callgraph.feature.source.feature.group
1.1.0.201305211237) requires
'org.eclipse.linuxtools.callgraph.feature.feature.group
[1.1.0.201305211237]' but it could not be found

InstallableUnit(org.eclipse.linuxtools.callgraph.feature.feature.group
[1.1.0.201305211237,1.1.0.201305211237]) is required by:
   ValidationSet(main)
 Contribution(Linux Tools)

MappedRepository(http://download.eclipse.org/linuxtools/update-kepler-rc1)

Feature(org.eclipse.linuxtools.callgraph.feature.source.feature.group
1.1.0.201305211237)

[attachment "linuxtools.b3aggrcon" deleted by David M
Williams/Raleigh/IBM] ___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Trying to aggregate source features using b3 aggregator editor

[Jeff Johnston]

I am trying to add the Linux Tools source features (without categories) 
so end-users can install them if desired.


When I add these features to the linuxtools.b3aggrcon file, I am getting 
an error trying to validate the aggregation.  The source features 
require the normal features and the b3 aggregator editor is saying that 
the feature is missing.


The missing feature in question is also in the b3aggrcon file (with 
category) and is found when validating the repository.  If I remove the 
source features, the aggregation validates fine.


Below is the actual message.  Is there something wrong with our repo or 
is it a known issue with the b3 aggregator editor trying to have new 
feature groups requiring other new feature groups?


I have attached the b3aggrcon file for reference.

-- Jeff J.

===

Cannot complete the install because one or more required items could not 
be found.
Missing requirement: C/C++ Call Graph Visualization Developer Resources 
1.1.0.201305211237 
(org.eclipse.linuxtools.callgraph.feature.source.feature.group 
1.1.0.201305211237) requires 
'org.eclipse.linuxtools.callgraph.feature.feature.group 
[1.1.0.201305211237]' but it could not be found


InstallableUnit(org.eclipse.linuxtools.callgraph.feature.feature.group 
[1.1.0.201305211237,1.1.0.201305211237]) is required by:

  ValidationSet(main)
Contribution(Linux Tools)

MappedRepository(http://download.eclipse.org/linuxtools/update-kepler-rc1)

Feature(org.eclipse.linuxtools.callgraph.feature.source.feature.group 
1.1.0.201305211237)



http://www.omg.org/XMI"; xmlns:aggregator="http://www.eclipse.org/b3/2011/aggregator/1.1.0"; label="Linux Tools">
  http://download.eclipse.org/linuxtools/update-kepler-rc1"; description="Linux Tools Updates">

  


  


  


  


  


  


  


  


  


  


  


  


  


  


 

 



 




















  
  
  

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Status and outlook for Kepler M3

[Jeff Johnston]

Thanks, that did it.  Thought I was losing my mind there...

I have updated Linux Tools for M3 +3.  Please make sure it gets to one of the 
builds please.

-- Jeff J.

- Original Message -
From: "Denis Roy" 
To: cross-project-issues-dev@eclipse.org
Sent: Wednesday, November 14, 2012 3:21:28 PM
Subject: Re: [cross-project-issues-dev] Status and outlook for Kepler M3

Sorry Jeff.

I've discontinued that redirect until it catches up.

Denis


On 11/14/2012 03:20 PM, Jeff Johnston wrote:
> Linux Tools has a backup M3 offering in place but I wanted to refresh today.
>
> I am experiencing problems using the b3 aggregator editor.  It claims it 
> can't find
> a number of repositories that have to be there, including the Linux Tools one 
> used in the previous successful aggregation:
> http://download.eclipse.org/linuxtools/update-kepler-m3.  I have verified the 
> repos exist by logging into build.eclipse.org.
>
> I was able to do so maybe an hour ago, but now it is not working.  Has 
> something changed very recently?
>
> I keep getting redirected to granite.eclipse.org and the repos are said to 
> not be there.  I want to load 
> http://download.eclipse.org/linuxtools/update-kepler-m3-b
>
> I could just make my change, but I would prefer to ensure it is loading.
>
> -- Jeff J.
>
> - Original Message -
> From: "David M Williams" 
> To: "Cross project issues" 
> Sent: Wednesday, November 14, 2012 2:53:29 PM
> Subject: [cross-project-issues-dev] Status and outlook for Kepler M3
>
>
> We've been without a clean build for past day or so but "we" just got one, so 
> I promoted it to staging.
>
> http://download.eclipse.org/releases/staging/
>
> I hope that everyone can check/confirm and get any other contributions made 
> by 5 PM, as today is +3 day of Kepler M3.
>
> Let us know if anyone needs an extra hour or two ... otherwise we'll assume 
> done at 5 PM (
>
> Looks like we are nearly complete with contributions being enabled with only 
> three remaining:
>
> emf-query2.b3aggrcon - org.eclipse.simrel.build
> jwt.b3aggrcon - org.eclipse.simrel.build
> soa-sca.b3aggrcon - org.eclipse.simrel.build
>
> But still several others with some features or repositories disabled:
>
> amp.b3aggrcon - org.eclipse.simrel.build
> dltk.b3aggrcon - org.eclipse.simrel.build (2 matches)
> egit.b3aggrcon - org.eclipse.simrel.build
> emf-emf.b3aggrcon - org.eclipse.simrel.build
> soa-bpel.b3aggrcon - org.eclipse.simrel.build
> tcf.b3aggrcon - org.eclipse.simrel.build (2 matches)
> tm.b3aggrcon - org.eclipse.simrel.build
> webtools.b3aggrcon - org.eclipse.simrel.build

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Status and outlook for Kepler M3

[Jeff Johnston]

Linux Tools has a backup M3 offering in place but I wanted to refresh today.

I am experiencing problems using the b3 aggregator editor.  It claims it can't 
find
a number of repositories that have to be there, including the Linux Tools one 
used in the previous successful aggregation:
http://download.eclipse.org/linuxtools/update-kepler-m3.  I have verified the 
repos exist by logging into build.eclipse.org.

I was able to do so maybe an hour ago, but now it is not working.  Has 
something changed very recently?

I keep getting redirected to granite.eclipse.org and the repos are said to not 
be there.  I want to load 
http://download.eclipse.org/linuxtools/update-kepler-m3-b

I could just make my change, but I would prefer to ensure it is loading.

-- Jeff J.

- Original Message -
From: "David M Williams" 
To: "Cross project issues" 
Sent: Wednesday, November 14, 2012 2:53:29 PM
Subject: [cross-project-issues-dev] Status and outlook for Kepler M3


We've been without a clean build for past day or so but "we" just got one, so I 
promoted it to staging. 

http://download.eclipse.org/releases/staging/ 

I hope that everyone can check/confirm and get any other contributions made by 
5 PM, as today is +3 day of Kepler M3. 

Let us know if anyone needs an extra hour or two ... otherwise we'll assume 
done at 5 PM ( 

Looks like we are nearly complete with contributions being enabled with only 
three remaining: 

emf-query2.b3aggrcon - org.eclipse.simrel.build 
jwt.b3aggrcon - org.eclipse.simrel.build 
soa-sca.b3aggrcon - org.eclipse.simrel.build 

But still several others with some features or repositories disabled: 

amp.b3aggrcon - org.eclipse.simrel.build 
dltk.b3aggrcon - org.eclipse.simrel.build (2 matches) 
egit.b3aggrcon - org.eclipse.simrel.build 
emf-emf.b3aggrcon - org.eclipse.simrel.build 
soa-bpel.b3aggrcon - org.eclipse.simrel.build 
tcf.b3aggrcon - org.eclipse.simrel.build (2 matches) 
tm.b3aggrcon - org.eclipse.simrel.build 
webtools.b3aggrcon - org.eclipse.simrel.build 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Last day for Juno SR1 contributions

[Jeff Johnston]

I made a change to Linux Tools b3aggrcon for RC4 and updated our repo, 
but another aggregation build was already started and it appears it 
won't finish until after 5 pm.


If another build doesn't get in by then, can you please start another  one?

Thanks,

-- Jeff J.

On 09/19/2012 03:03 AM, David M Williams wrote:

Here we are already, Juno SR1 RC4 +3.

I did have to temporarily disable Jubula to get a green build but I know
they are working on the issue, if not fixed already.

5 PM today, Wednesday, (Eastern) is the deadline, unless someone speaks
up that they need a few extra hours.

And then we begin "quiet week". This is a good time for committers and
adopters to do some final testing. Even if a bad bug or regression was
found, and could not be fixed in "common repo" due to being too late,
projects can always produce their own update sites with patched
features, or work on documenting workarounds.  Better to know ahead of
time, than be surprised. Remember, any requests for respins need to go
through the formal exception process, and it has to be something pretty
big that can not be fixed by a normal patch feature, or similar.

While there is no formal "Final Daze" document for service releases, it
would be good for simrel engineers to review the main one for Juno, at
http://wiki.eclipse.org/Juno/Final_Daze

The principles are the same ... clean up old stuff so mirrors don't get
full. Promote zips and repositories early to make sure they get well
propagated to mirrors but "leave invisible" until Friday, 9/28, so we do
not prematurely "release" anything before its time, in an uncoordinated
fashion that's confusing to end-users (if not the rest of us).

Don't forget, if any of you changed or fixed substantial parts of your
"help docs", you may want to open a bug in cross-project list to have
webmasters update the info center for Juno SR1.

Lastly, remember to change the repository reports ... I still see one
missing "about.html" file 
http://build.eclipse.org/simrel/juno/reporeports/

Thanks everyone,


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Kepler metadata flag

[Jeff Johnston]

I set it +1 yesterday.  Just looking again, it shows +1 in the Metadata.

-- Jeff J.

On 08/15/2012 11:34 PM, Wayne Beaton wrote:

Is Linux Tools really +0?

Wayne

On 08/15/2012 04:41 PM, Wayne Beaton wrote:

The Kepler flag has been added. Join away!

Wayne

On 08/15/2012 04:44 AM, Igor Vinnykov wrote:


Hello,

The Kepler Simultaneour Release wiki page
(http://wiki.eclipse.org/Kepler) refers the simultaneousrelease flag
in metadata, but at the current moment there is no "Kepler" value for
this flag. Also the list of participating projects
(http://www.eclipse.org/projects/releases/releases.php?release=kepler) shows
data from Juno.

Please announce here the metadata properties that should be
configured in order to join the Kepler release once these properties
will be available in metadata configuration. It will be better to
configure these properties together with Kepler scheduling. Previous
times I had to check these properties multiple times to find the
moment when they can be configured and once forgot to recheck and
failed M4 due date because of this.

Best regards,

Igor Vinnykov

Subversive Team


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org  

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects 


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects 


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Failures in the Hudson Juno run.aggregator job?

[Jeff Johnston]

I noticed that the Juno run.aggregator job is failing on Hudson after a 
bunch of RC4 changes.  Is someone assigned to each of the issues (other 
than David)?


-- Jeff J.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Status and outlook for RC3

[Jeff Johnston]

Fixed for the Linux Tools plugins.  Linux Tools b3aggrcon updated to 
point to the new build.


-- Jeff J.

On 06/06/2012 12:09 AM, David M Williams wrote:

Admittedly, there is one day left for Juno RC3, but I can't help but
point out several (27) missing "about.html" files.

http://build.eclipse.org/juno/simrel/reporeports/reports/layoutCheck.txt

Plus, according to another report,

http://build.eclipse.org/juno/simrel/reporeports/reports/licenseConsistency.html


there are 12 features missing "license" (EUA) files in features.

The observant will notice that the two reports seem to say different
things (the first saying none are missing license files in features, the
latter saying 12 are missing).

And they are different things. The first report checks the feature files
themselves and determines if the file is there or not.

But, the second report is for the "license info" that is part of the
repository content metadata, which arguably is more important, since it
is the one that is presented to a users before they install something
and the users asked "do you agree ... ?" before installing something.

So, the license file can be contained in the feature itself (first
report) but not "published" correctly to the p2 repository. You'll
notice all the "missing licenses" say "%license" which is actually a
good sign ... that probably means there's just something missing in the
feature.properties file or something (but ... there are a couple of
methods of "publishing" features ... so, you'll have to check.)

To give one compliment though, Almost everyone one has finally moved up
to the 2011 license. Last year, there were several hundred that had not.

  * Features with conforming (2011) license: 845
  * Features with old (2010) license: 21



Thanks all,


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Hudson Juno aggregation build failure and ACTF

[Jeff Johnston]

I updated Linux Tools for RC2, but ran into an issue with ACTF not 
finding one of its required features.  When I disabled this locally, the 
aggregation validated fine.  The last build failed with updates from 
Linux Tools, ACTF, and Webtools.  I updated my local repository so I do 
not know if the ACTF problem I ran into is the same one causing the 
build failure.


-- Jeff J.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Linux Tools is trying to get an update in today

[Jeff Johnston]

The Linux Tools build is missing a few features that should be there and 
I am attempting to build and add them in today (waiting for an executor).


We already have an RC2 build offering in place and aggregated 
successfully so if the build can't be done in time, we will wait until RC3.


-- Jeff J.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] p2.mirrorsURL property - how do different projects handle this?

[Jeff Johnston]

For our Linux Tools project, we use tycho to build.  We want to have the 
p2.mirrorsURL property specified in artifacts.jar, but we haven't found 
a way to do this other than manually unzip artifacts.jar, edit 
artifacts.xml to add the p2.mirrorsURL property to the repository 
properties, then rezip; all done post-build.


Do any other projects out there have any insights on how to do this more 
efficiently/automatically?


-- Jeff J.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Status and Outlook for Indigo SR2

[Jeff Johnston]

Linux Tools has just rebuilt and updated the Indigo linuxtools.b3aggrcon 
file.  This was to make a p2 fix for bug #371302 regarding the renamed 
feature problem updating SR1 to SR2.


Please include this in a re-spin if you weren't planning to do one at 
5:00 pm.


-- Jeff J.


On 02/15/2012 03:11 PM, David M Williams wrote:



We did finally get a green build, and I am promoting those bits
to .../releases/maintenance as I type this note.

Normally, I'd say 5 PM is last chance for any new submissions. And mean it.
This time, I'll say that, but be more forgiving if someone says "wait, we
didn't get our final bits done yet".

With all the infrastructure problems today, I am not sure if everyone got
their final bits built and submitted in time? I lost track of all the
emails, especially with the 50 failed contributions email problem.

So, while we still don't required positive sign-off, please post to this
list soon (by 5 PM Eastern, 7 PM at latest) if you need a re-spin due to
infrastructure delays (or, if you need a respin for other reasons .. do NOT
blame it on the infrastructure! We can tell the difference. :)

Thanks


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Hudson appears to be broken

[Jeff Johnston]

Is anyone able to get an executor?  I have been trying for a while to 
start a Linux Tools build to fix a feature rename issue from SR1 to SR2.


-- Jeff J.

On 02/15/2012 12:50 PM, Trip Gilman wrote:

Voicetools indigo build is also died with:

FATAL: cannot assign instance of hudson.model.StreamBuildListener to field
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.listener of type
hudson.model.TaskListener in instance of
hudson.scm.SubversionSCM$CheckOutTask
java.lang.ClassCastException: cannot assign instance of
hudson.model.StreamBuildListener to field
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.listener of type
hudson.model.TaskListener in instance of
hudson.scm.SubversionSCM$CheckOutTask
at
java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClas
s.java:2032)
at
java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1212)
at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1953)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at hudson.remoting.UserRequest.deserialize(UserRequest.java:178)
at hudson.remoting.UserRequest.perform(UserRequest.java:98)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:283)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.j
ava:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
908)
at java.lang.Thread.run(Thread.java:619)

Trip Gilman



On 2/15/12 8:03 AM, "Greg Watson"  wrote:


One of our builds is stuck with the following:

Started by user gwatson
Building remotely on hudson-slave1
Checkout:ptp-photran-release /
/opt/users/hudsonbuild/workspace/ptp-photran-release -
hudson.remoting.Channel@66e43eb8:hudson-slave1
Using strategy: Default
Last Built Revision: Revision a6fd57d8b335e2ee13c8d0a17d1f9584771a6e9f
(origin/ptp_5_0)
FATAL: cannot assign instance of hudson.EnvVars to field
hudson.plugins.git.GitSCM$3.val$environment of type hudson.EnvVars in
instance of hudson.plugins.git.GitSCM$3

java.lang.ClassCastException
: cannot assign instance of hudson.EnvVars to field
hudson.plugins.git.GitSCM$3.val$environment of type hudson.EnvVars in
instance of hudson.plugins.git.GitSCM$3
at
java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamCla
ss.java:2032)

at
java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1212)

at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1953)

at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)

at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)

at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)

at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)

at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)

at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)

at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)

at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)

at
hudson.remoting.UserRequest.deserialize(UserRequest.java:178)

at
hudson.remoting.UserRequest.perform(UserRequest.java:98)

at
hudson.remoting.UserRequest.perform(UserRequest.java:48)

at
hudson.remoting.Request$2.run(Request.java:283)

at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at
java.util.concurrent.FutureTask.run(FutureTask.java:138)

at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.
java:886)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
:908)

at
java.lang.Thread.run(Thread.java:619)
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


_

[cross-project-issues-dev] How to get update site to show up in available site list?

[Jeff Johnston]

The Linux tools update site does not show up in the list of available 
update sites for Indigo SR1.


The features in Linux tools have the update site specified in the 
feature.xml:


   
  url="http://download.eclipse.org/technology/linuxtools/update"/>

   


What is needed so Eclipse will add/find the update site automatically as 
it seems to do for other projects such as cdt, emf, dtp?


-- Jeff J.

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev