Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[] [Bug 361287] New: using unreleased thirdparty code in eclipse project development builds
Product/Component: Community / Architecture Council

           Summary: using unreleased thirdparty code in eclipse project
                    development builds
    Classification: Eclipse Foundation
           Product: Community
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Architecture Council
        ReportedBy: igor@xxxxxxxxxxxxxx

If I understand parallel IP process [1] correctly, I have to submit CQs for all
thirdparty dependencies and wait for checkintocvs before I can push
corresponding code changes to my project git repository. I also believe
that only released versions of thirdparty code can be submitted for IP

If I follow this process to the letter, it more or less prevents
development of new features that require tightly coupled changes to
eclipse and non-eclipse code. Taking m2e and maven as an example, here
is what it will take to introduce new feature that requires changes to
both projects

1. make change to m2e and maven, push maven changes to apache
2. wait for the next maven release (assume this takes 3 months)
3. open CQ for the new maven version and get checkintocvs (assume this takes
two weeks)
4. push m2e changes to eclipse and wait for next the milestone (assume this
takes two weeks)
5. receive negative user, repeat

Is there a way to stay within Eclipse legal requirements and still consume
development versions of thirdparty code or I have to do this outside of


Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Back to the top