My point is you should have discussed that before having projects depend on 
code in your sandbox or releasing code in your sandbox.

So undo these changes and releases and then start a proper discussion, 
explaining us why you want an "Amdatu Commons" subproject. If there is 
consensus, then we have to go to the board (because they're the only ones who 
can formally approve that).

For the record, in the platform we had a discussion about the "utilities" that 
were used amongst different sub projects and decided against those (see 
http://jira.amdatu.org/jira/browse/AMDATU-264) so I don't think having an 
"Amdatu Commons" subproject would be a good idea.

Greetings, Marcel

On Feb 3, 2012, at 9:14 AM, Ivo Ladage-van Doorn wrote:

> Hi Marcel,
>  
> I agree that this is not an ideal situation, but there are currently no 
> alternatives. This particular bundle is shared among the subprojects Big 
> Data, OpenSocial and Auth. It is not part of these subprojects and has an 
> independent release cycle. With removing various ‘generic’ bundles like this 
> one from the platform in the upcoming release, much more of these bundles 
> will arise.
> So we need to think about how to deal with bundles like these. I suggest to 
> introduce an ‘Amdatu Commons’ subproject, an umbrella project for generic 
> bundles/utilities used by the subprojects but not part of the platform. If 
> such a subproject is available, I can move the code from my sandbox to that 
> subproject. Until then, it remains in my sandbox.
>  
> Regards, Ivo
>  
> From: Marcel Offermans [mailto:[email protected]] 
> Sent: donderdag 2 februari 2012 17:44
> To: [email protected]
> Cc: Ivo Ladage-van Doorn
> Subject: Subprojects that depend on sandboxes that have been released?
>  
> Hello Ivo,
>  
> I was highly surprised today that I could no longer build the trunk of our 
> OpenSocial project, even though the Bamboo build works.
>  
> After some investigation, it turns out that OpenSocial depends on something 
> called org.amdatu.commons:org.amdatu.commons.restdoclet:jar:1.0.3, which has 
> a package name that does not seem to belong to any of our subprojects, nor is 
> it part of the platform. After browsing around it seems to be in your 
> sandbox: 
> http://subversion.amdatu.org/viewvc/amdatu/sandbox/ivol/amdatu-commons/
>  
> No project should ever depend on something in someone's sandbox.
>  
> The next question was, why does Bamboo not fail. It seems that there were 
> even versions released from this sandbox, as can be seen here: 
> http://repository.amdatu.org/releases/org/amdatu/commons/org.amdatu.commons.restdoclet/
>  
> I don't remember us ever voting on any of those releases, nor did we ever 
> agree to even do releases from sandboxes (which makes no sense whatsoever).
>  
> Please:
> a) immediately remove all releases from that folder;
> b) remove all dependencies of OpenSocial on stuff in a sandbox.
>  
> Greetings, Marcel
>  
> _______________________________________________
> Amdatu-developers mailing list
> [email protected]
> http://lists.amdatu.org/mailman/listinfo/amdatu-developers

_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers

Reply via email to