[tycho-user] Directory structure for pom-less build

[M***@Diamond.ac.uk]

Background: We're looking at moving away from Buckminster to Maven/Tycho to build our Eclipse RCP products.

It was suggested that a pom-less build was the best approach, but looking at the documentation, all the examples assume a fairly specific directory structure, something like:

project/
-- .mvn/
-- bundles/
---- bundle1/
---- bundle2/
-- features/
---- feature1/
---- feature2/
-- products/
---- product1/
---- product2/

Is that structure really required?

Our code lives across a number of repositories. Worse, we need to ignore some of the projects (bundles/features) that exist in the repositories - directories containing code might exist, but the code might not even compile. In the IDE that's not a problem, because we simply don't import those projects into the Eclipse workspace, so they are invisible to the build.

Can Tycho pom-less build handle this - does it have access to the Eclipse workspace, so that it knows what projects exist and where on disk they are?

I guess I'm missing some basic concepts here - I can see that Tycho knows about Eclipse-type things (features, products etc), but does it also know about Eclipse workspaces and what is/is not in them?

Thanks for any guidance!

Matthew

[Jonah Graham]

Hi Matthew,

The pom-less builds are not 100% pom free, you just don't need pom files in
the modules that are plugins (or features). You still need pom.xml in the
parent directory,listing the subdirectories that should be included in the
module(s) tags. (modules don't have to be subdirectories, that is just
common).

The structure you have should not be a problem.

HTH
Jonah

Post by M***@Diamond.ac.uk
Background: We're looking at moving away from Buckminster to Maven/Tycho
to build our Eclipse RCP products.
It was suggested that a pom-less build was the best approach, but looking
at the documentation, all the examples assume a fairly specific directory
project/
-- .mvn/
-- bundles/
---- bundle1/
---- bundle2/
-- features/
---- feature1/
---- feature2/
-- products/
---- product1/
---- product2/
Is that structure really required?
Our code lives across a number of repositories. Worse, we need to ignore
some of the projects (bundles/features) that exist in the repositories -
directories containing code might exist, but the code might not even
compile. In the IDE that's not a problem, because we simply don't import
those projects into the Eclipse workspace, so they are invisible to the
build.
Can Tycho pom-less build handle this - does it have access to the Eclipse
workspace, so that it knows what projects exist and where on disk they are?
I guess I'm missing some basic concepts here - I can see that Tycho knows
about Eclipse-type things (features, products etc), but does it also know
about Eclipse workspaces and what is/is not in them?
Thanks for any guidance!
Matthew
--
This e-mail and any attachments may contain confidential, copyright and or
privileged material, and are for the use of the intended addressee only. If
you are not the intended addressee or an authorised recipient of the
addressee please notify us of receipt by returning the e-mail and do not
use, copy, retain, distribute or disclose the information in or attached to
the e-mail.
Any opinions expressed within this e-mail are those of the individual and
not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any
attachments are free from viruses and we cannot accept liability for any
damage which you may sustain as a result of software viruses which may be
transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England
and Wales with its registered office at Diamond House, Harwell Science and
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
_______________________________________________
tycho-user mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user

[Dirk Fauth]

Not sure if it helps in answering your question, but I wrote a blog post
about that a while ago

http://blog.vogella.com/2015/12/15/pom-less-tycho-builds-for-structured-environments/

Post by Jonah Graham
Hi Matthew,
The pom-less builds are not 100% pom free, you just don't need pom files
in the modules that are plugins (or features). You still need pom.xml in
the parent directory,listing the subdirectories that should be included in
the module(s) tags. (modules don't have to be subdirectories, that is just
common).
The structure you have should not be a problem.
HTH
Jonah

Post by M***@Diamond.ac.uk
Background: We're looking at moving away from Buckminster to Maven/Tycho
to build our Eclipse RCP products.
It was suggested that a pom-less build was the best approach, but looking
at the documentation, all the examples assume a fairly specific directory
project/
-- .mvn/
-- bundles/
---- bundle1/
---- bundle2/
-- features/
---- feature1/
---- feature2/
-- products/
---- product1/
---- product2/
Is that structure really required?
Our code lives across a number of repositories. Worse, we need to ignore
some of the projects (bundles/features) that exist in the repositories -
directories containing code might exist, but the code might not even
compile. In the IDE that's not a problem, because we simply don't import
those projects into the Eclipse workspace, so they are invisible to the
build.
Can Tycho pom-less build handle this - does it have access to the Eclipse
workspace, so that it knows what projects exist and where on disk they are?
I guess I'm missing some basic concepts here - I can see that Tycho knows
about Eclipse-type things (features, products etc), but does it also know
about Eclipse workspaces and what is/is not in them?
Thanks for any guidance!
Matthew
--
This e-mail and any attachments may contain confidential, copyright and
or privileged material, and are for the use of the intended addressee only.
If you are not the intended addressee or an authorised recipient of the
addressee please notify us of receipt by returning the e-mail and do not
use, copy, retain, distribute or disclose the information in or attached to
the e-mail.
Any opinions expressed within this e-mail are those of the individual and
not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any
attachments are free from viruses and we cannot accept liability for any
damage which you may sustain as a result of software viruses which may be
transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England
and Wales with its registered office at Diamond House, Harwell Science and
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
_______________________________________________
tycho-user mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user

_______________________________________________
tycho-user mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user

[Wim Jongman]

I managed to move Nebula to a pom-less build but I could not get Sonar
working with it so I reverted.

Discussion is here:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=493984

Post by Dirk Fauth
Not sure if it helps in answering your question, but I wrote a blog post
about that a while ago
http://blog.vogella.com/2015/12/15/pom-less-tycho-builds-
for-structured-environments/

Post by Jonah Graham
Hi Matthew,
The pom-less builds are not 100% pom free, you just don't need pom files
in the modules that are plugins (or features). You still need pom.xml in
the parent directory,listing the subdirectories that should be included in
the module(s) tags. (modules don't have to be subdirectories, that is just
common).
The structure you have should not be a problem.
HTH
Jonah

Post by M***@Diamond.ac.uk
Background: We're looking at moving away from Buckminster to Maven/Tycho
to build our Eclipse RCP products.
It was suggested that a pom-less build was the best approach, but
looking at the documentation, all the examples assume a fairly specific
project/
-- .mvn/
-- bundles/
---- bundle1/
---- bundle2/
-- features/
---- feature1/
---- feature2/
-- products/
---- product1/
---- product2/
Is that structure really required?
Our code lives across a number of repositories. Worse, we need to ignore
some of the projects (bundles/features) that exist in the repositories -
directories containing code might exist, but the code might not even
compile. In the IDE that's not a problem, because we simply don't import
those projects into the Eclipse workspace, so they are invisible to the
build.
Can Tycho pom-less build handle this - does it have access to the
Eclipse workspace, so that it knows what projects exist and where on disk
they are?
I guess I'm missing some basic concepts here - I can see that Tycho
knows about Eclipse-type things (features, products etc), but does it also
know about Eclipse workspaces and what is/is not in them?
Thanks for any guidance!
Matthew
--
This e-mail and any attachments may contain confidential, copyright and
or privileged material, and are for the use of the intended addressee only.
If you are not the intended addressee or an authorised recipient of the
addressee please notify us of receipt by returning the e-mail and do not
use, copy, retain, distribute or disclose the information in or attached to
the e-mail.
Any opinions expressed within this e-mail are those of the individual
and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any
attachments are free from viruses and we cannot accept liability for any
damage which you may sustain as a result of software viruses which may be
transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in
England and Wales with its registered office at Diamond House, Harwell
Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
_______________________________________________
tycho-user mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user

_______________________________________________
tycho-user mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user

_______________________________________________
tycho-user mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user