Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Ready for Mars.2 ?

The .../
repo was for that "last minute rebuild" we did for one project.
(It was going to be THE release, but we ended up releasing on 201510021000 due to the required re-spin.)

If you are still "seeing" that in a maintenance branch, then I suspect you are looking at Mars_maintenance.1 (which was the branch used for that one purpose of the Mars.1 respin.)
The maintenance branch for Mars.1 and Mars.2 is named Mars_maintenance.

From what I see, Riena is still being built from .../rt/riena/6.1.0.RC1/e4-rap/. So, if there are "warnings" in the report, I suspect they were always there.

But, if you want to check, the "repo reports" for Mars.1 are available at

"keep 'um coming" if there are more questions or comments.


From:        Christian Campo <christian.campo@xxxxxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        02/04/2016 02:48 AM
Subject:        Re: [cross-project-issues-dev] Ready for Mars.2 ?
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

Hi David,

Another non-sleeping project here :-). The intention of Riena is to contribute exactly what we contributed to Mars itself. Every contribution file changed ? I didnt change the Riena contribution file but I noticed that YOU did.

You changed the contribution for Riena from

I am pretty sure that the simrel reports where clean for Mars for Riena. Now it is complaining about all sort of things. One is that there are no pack200 files. Fact is that the original URL contains pack200 files, while the release location does not.

What was the intention of changing the URL in Riena’s contribution ? Should I change it back ?

Let me know what the next steps should be….


Von: <cross-project-issues-dev-bounces@xxxxxxxxxxx> on behalf of Alexander Nyßen <nyssen@xxxxxxxxx>
Antworten an:
Cross issues <
Donnerstag, 4. Februar 2016 um 08:29
Cross issues <
Re: [cross-project-issues-dev] Ready for Mars.2 ?

Hi David,

I was wondering about your first statement also, as GEF is not contributing something new to Mars.2 either (we are fully concentrating on our 4.0.0 release for Neon). Our contribution to Mars.2 should be the same as that to Mars, and as far as I can see that is indeed the case.  


Am 04.02.2016 um 07:08 schrieb Ed Willink <ed@xxxxxxxxxxxxx>:

Hi David

On 03/02/2016 22:29, David M Williams wrote:
- Every contribution file has changed since Mars.1. Also good. (i.e. no projects are just sleeping and forgot to update :)

You might want to review your query. qvtd.b3aggrcon was last changed by me on 26 June, and by you on 14 July.

We are certainly not sleeping, and did not forget to update. Just working very hard to support the functionality required for graduation to 1.0.0.

And ... worst of all, IMHO, some "old" third party jars are still being used, which implies to me someone is not using the latest version of Orbit (R20151221205849).
But if a project has no maintenance to contribute, I thought no rebuild/contribution was required and so of course an old Orbit would be in use. (I don't think that QVTd imposes tight bounds on Orbit contributions.)


       Ed Willink

cross-project-issues-dev mailing list

To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Dr. Alexander Nyßen
Principal Engineer

Telefon: +49 (0) 231 / 98 60-202
Telefax: +49 (0) 231 / 98 60-211
Mobil: +49 (0) 151 /  17396743

itemis AG
Am Brambusch 15-24
44536 Lünen

Rechtlicher Hinweis:

Amtsgericht Dortmund, HRB 20621

Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus

Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer Fiorentino

compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22

Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz

Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
USt-IdNr. DE207665352
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top