Community
Participate
Working Groups
Build Identifier: Find attached some initial code that we are planning to share with the community. The attached code has two components, core and ui. This separation is useful for the case when some headless tasks are to be performed without the UI. It provides these features: -OSGi facet configuration, that does not exclude other project facets. -Creating OSGi Bundles, and OSGi Web Bundles -Importing and Exporting Bundles. -Support for OSGi Fragments. -Converting existing projects to OSGi Bundles. -Java projects -PDE Plugins -JEE Web projects -Utility jars -JPA -Converting PDE Fragments to OSGi Fragments -Flexible Bundle Root Reproducible: Always
Created attachment 189278 [details] Initial drop
Zina, it's great you kicked off your initial contribution. The next step is to file a CQ to trigger the IP Review. This is done using the Foundation Portal: http://portal.eclipse.org/ I suggest that you submit this CQ. But you first must be provisioned as a committer. I see that the paperwork process has not finished yet. Feel free to contact the EMO (emo@eclipse.org) if you feel there is a delay that is more than expected.
In the mean time, please take a look at the code that is already contributed in the Git repository. I think your contribution has some overlap with the code in the org.eclipse.libra.facet.* plugins. We need to see how to merge the different contributions in a way that best fits all adopter. We will also take a look at the code you've just attached to get familiar with your contribution. You can obtain information about the Git repository from the project's summary page: http://www.eclipse.org/projects/project_summary.php?projectid=webtools.libra
Zina, the CQ has been already approved for some time. Can we have the code pushed to Git by M2?
I have been under some very limited resources to do so. The source code is in teh attachment, but I am anticipating long time trying to merge that with the existing source in Git. I am not sure how much we can do in terms of merging. Would it be useful if we check in our plugins as-is without merging ?
Perhaps, I good first step is to submit to code in a separate branch in Git, e.g. "ibm", "zina", etc. This way the master branch will not be affected. Then I can help merging your contribution with the existing code.
Adding to the Juno plan and changing the title with more descriptive one.
Zina, do you need any help with Git to commit the code?
M2 passed away. Let's try doing this for M3.
