Re: [cross-project-issues-dev] Status and outlook for Kepler M4 +3

[David M Williams <david_williams@xxxxxxxxxx>]

This commit, did "break" aggregation.
The reason is you removed the feature from your file, but its still "listed"
in the "SOA Development" Category. When ever features are added
or removed, I recommend using the b3 aggregator editor. It often effects
not only your file, but the simrel.b3aggr file, where categories are defined.
The "validate" action will say if the model is still valid and
consistent. Both your file, and simrel.b3aggr must to checked in together.

Perhaps you did make the change correctly,
and simply forgot to check-in the simrel file? But, in any case, we don't
need to re-spin now, for a removed feature, since it was disabled anyway,
but will have to be fixed before we could aggregate, again.
 

commit e8b21c7ce2d64654edce952cac08c5f608031925
Author: vzurczak <vincent.zurczak@xxxxxxxxxxxxxx>
Date:   Thu Dec 20 15:23:23 2012
+0100

    Remove a disabled feature.
    
    Signed-off-by: vzurczak
<vincent.zurczak@xxxxxxxxxxxxxx>




From:      
 Vincent Zurczak <vincent.zurczak@xxxxxxxxxxxx>
To:      
 cross-project-issues-dev@xxxxxxxxxxx,

Date:      
 12/20/2012 09:35 AM
Subject:    
   Re: [cross-project-issues-dev]
Status and outlook for Kepler M4 +3
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Done.
However, I made a Git merge. I just hope I did not break anything. :|

             Vincent.



Le 20/12/2012 15:05, Vincent Zurczak a écrit :
Hi,

I will handle the soa.bpel warning before this evening.

Cheers,

              Vincent.


Le 19/12/2012 22:51, David M Williams a écrit :
It is almost 5 PM (Eastern) and not
heard anyone ask for "wait" ... though sounded implied by some
messages here? 

I do see that amp is completely disabled (at the repository level): 

amp.b3aggrcon - org.eclipse.simrel.build 

These three projects have a feature or two disabled. Not sure if the features
are no longer needed/used or if a respin is needed now that others are
up to date? 

dltk.b3aggrcon - org.eclipse.simrel.build (2 matches)
egit.b3aggrcon - org.eclipse.simrel.build 
soa-bpel.b3aggrcon - org.eclipse.simrel.build 

If it is a matter of deleting unused one, there is no need to do that today,
but would appreciate the "cleanup" next cycle, just so it is
easier for me to tell what's what. 

I'll wait a few more hours (till 7 PM, Eastern) just to see if there's
any stragglers, and if not, turn off the aggregation job until after M4.

Thanks all, 

-- 
Vincent Zurczak

Phone: +33 (0) 6 40 28 86 57
Linagora: www.linagora.com

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


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

Attachment: STG06729
Description: Binary data

Attachment: STG45220
Description: Binary data

Attachment: STG61102
Description: Binary data

Attachment: STG27331
Description: Binary data