| Hi, Camille,
Perhaps, but that would entail updating the central Catalogue to point to its new location, and it makes sense to keep it together with the other releng materials (it needs regular maintenance using the same tool as we use for updating the top-level poms).
I think perhaps the problem is just that the setup model, itself, configures the URI redirection in everybody's installations. It's only needed for testing local changes to the model, so I think it would be better just to remove the redirection and let users add it to their own configuration as needed for testing the setup, in which case they'll be working on the master branch a priori.
Christian
Hi Christian, Would it make sense to commit the Oomph setup to the Papyrus Website repository instead? The Website has a single master/ branch (And is already used to provide the discovery site model for all versions, for example) Camille
Hi,
I have pushed some fixes to the Oomph setup model that should make the dynamic working set rules work correctly on Windows platform. Please let me know if that is still a problem.
I also removed the releng/org.eclipse.papyrus.oomph project from the Luna maintenance branch (streams/1.0-maintenance). It only contained the setup model, which on that branch was obsolete. To aid in development of the setup model, it specifies a URI redirection that maps the http location of the model in the Oomph Catalogue to its location in the local git clone. Because the setup model is only maintained on the master branch, when the local git clone has the Luna maintenance branch checked out, this mapping actually resolves to an obsolete model that breaks the Oomph Installer tool rather badly. So, removing it from the branch ensures that mapping doesn't take effect and the Oomph Installer only sees the live version of the model in the catalogue.
Unfortunately, this does mean that every time we branch a new maintenance stream, we'll have to delete the setup model again from that branch. I would prefer to find a way to make the URI redirection effective only when the master branch is checked out, but I don't know how that could be done.
Cheers,
Christian Hi Christian,
I re-ran the setup from within the workspace but the result is identical, a bad build of working sets. I was careful to look the log during use but nothing wrong happened. I attached corresponding setup log file.
This is not blocking but I don't understand why only this task fails while others, from my point of view more complex, succeed.
Regards
Gabriel
Le 15/09/2014 14:43, Christian W. Damus a écrit :
Hi, Gabriel,
Yes, I've seen that on occasion, that the working sets aren't configured at all, but usually that's because something went wrong in the project import phase. Do you see any problems indicated in the Oomph log? Re-running the setup from within the workspace (the yellow and green arrows button in the toolbar) might clear up the problem.
Cheers,
Christian Hi Christian,
I have just tested new setup model and I was able to create an IDE based on Eclipse Luna MDT without no major trouble. Thanks.
Only met issue is about the build of working directories. When build is finished, working directories were created but no projects were imported inside despite correct import of projects in common working directory "Other projects".
Regards
Gabriel
Le 12/09/2014 22:37, Christian W. Damus a écrit :
Hi, Gabriel,
The Papyrus setup model now no longer installs EcoreTools into your IDE. Let me know if you have any further trouble.
Christian Hi Team, I tried to build my IDE with Oomph for both versions (Luna and Mars) but I always have the same error during dependencies resolution. I used build 453 of Oomph installer. The log file is attached for both tries. Regards Gabriel --
| | Gabriel PASCUAL
Software Engineer
|
6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex - FRANCE
www.all4tec.net |
|
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev --
| | Gabriel PASCUAL
Software Engineer
|
6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex - FRANCE
www.all4tec.net |
|
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev --
| | Gabriel PASCUAL
Software Engineer
|
6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex - FRANCE
www.all4tec.net |
|
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________ mdt-papyrus.dev mailing list mdt-papyrus.dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
|
