Bower Registration

[fabricematrat]

Find a solution to allow bower registration but keep only one version for all modules

[mathbruyen]

There are already two modules just on the javascript side and Bower really expects to have a 1-to-1 relation between package and repository. More packages are expected, for example for having predefined serializers.

So I can imagine one single package out of which one would cherry-pick what they need. From my understanding of Bower it really exposes paths to the source code. It sounds quite dangerous to link to javascript\core\src\index.js or javascript\generator\src\index.js.

Then one could obviously imagine splitting the repository, but I don't really like it because if one wants to do a cross module change in an 'atomic' manner, that would no longer work.

So what should be published under Bower?

[fabricematrat]

We could either have git sub modules for each js module or one single
package as you suggested, but for IOS Cocoa spec we will have the same
issue.
Not that simple :)

On Mon, Feb 17, 2014 at 11:30 AM, Mathieu Bruyen
[email protected]:

There are already two modules just on the javascript side and Bower really
expects to have a 1-to-1 relation between package and repository. More
packages are expected, for example for having predefined serializers.

So I can imagine one single package out of which one would cherry-pick
what they need. From my understanding of Bower it really exposes paths to
the source code. It sounds quite dangerous to link to
javascript\core\src\index.js or javascript\generator\src\index.js.

Then one could obviously imagine splitting the repository, but I don't
really like it because if one wants to do a cross module change in an
'atomic' manner, that would no longer work.

So what should be published under Bower?

Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-35245044
.

Best regards,

http://rivieragug.org/
http://3musket33rs.github.com/

[mathbruyen]

I may be wrong because I do not heavily use them but I think if you make changes inside submodules it won't appear on a git status from the global root, and so one needs to remember every place a change has been made. Otherwise it would be tempting.

[mathbruyen]

As part of the termination reworking, both packages have been merged into one. A solution for upcoming releases would then be to publish this unified core module in Bower and see when new modules (serializers, source providers) are needed how to publish them too.

Currently working on it in the termination branch.