You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we need to migrate our existing headless PDEBuild RCP applications by a the tycho build. In our situation we have all or plugins already build and they are stored in our maven repo. We don't want to rebuild them. Similarly, all our features and the product file are accessible as maven artifacts. The old PDEBuild was able to grab all these things and to create the executable including the products plugins and feature and p2 folder.
How can I use a headless tycho build to do just this bare minimum of work? Ideally we would just like to reuse our existing features and thirdparty bundles (that is the Eclipse RCP plugins for a dedicated Eclipse version that we also have stored in our artifactory). Is this possible and if so how?
I read the part about the recommended layout, but my impression is that the bundles subfolder exists for projects to be build. But I don't want to build them, we have already build them as OSGi compatible jars. We only want that the PDEBuild replacement is able to honor the possible feature.xml directives that say which bundles need to to be unpacked and which not. In PDEBuild it was possible to specify a folder for everything pre-build (The thirdparty folder). How can I specify such a "thirdparty" folder for things that have been prebuild? (As I said: In our case we have all bundles rebuild, we just want to invoke a process that creates the final executable including the folder structure for plugins, features, and p2 directory.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, we need to migrate our existing headless PDEBuild RCP applications by a the tycho build. In our situation we have all or plugins already build and they are stored in our maven repo. We don't want to rebuild them. Similarly, all our features and the product file are accessible as maven artifacts. The old PDEBuild was able to grab all these things and to create the executable including the products plugins and feature and p2 folder.
How can I use a headless tycho build to do just this bare minimum of work? Ideally we would just like to reuse our existing features and thirdparty bundles (that is the Eclipse RCP plugins for a dedicated Eclipse version that we also have stored in our artifactory). Is this possible and if so how?
I read the part about the recommended layout, but my impression is that the bundles subfolder exists for projects to be build. But I don't want to build them, we have already build them as OSGi compatible jars. We only want that the PDEBuild replacement is able to honor the possible feature.xml directives that say which bundles need to to be unpacked and which not. In PDEBuild it was possible to specify a folder for everything pre-build (The thirdparty folder). How can I specify such a "thirdparty" folder for things that have been prebuild? (As I said: In our case we have all bundles rebuild, we just want to invoke a process that creates the final executable including the folder structure for plugins, features, and p2 directory.
Beta Was this translation helpful? Give feedback.
All reactions