Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 482474 - Provide configuration for pomless builds
Summary: Provide configuration for pomless builds
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 4.9   Edit
Assignee: Lars Vogel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 535382
  Show dependency tree
 
Reported: 2015-11-18 08:33 EST by Lars Vogel CLA
Modified: 2018-06-01 06:43 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 2015-11-18 08:33:48 EST

    
Comment 1 Lars Vogel CLA 2015-11-18 08:43:01 EST
Tycho 0.24 introduced the option to build pomless. We should enable platform.ui for this. Using this feature would be done via separate bugs.
Comment 2 Eclipse Genie CLA 2015-11-18 10:17:57 EST
New Gerrit change created: https://git.eclipse.org/r/60717
Comment 3 David Williams CLA 2015-12-02 09:52:33 EST
I have reservations about using "pom-less builds". 

What problem is it solving, for us? 

I am assuming there is no way we could ever go completely pom-less, so it does not seem like too much of an enhancement, and might just be more confusing. 

I am assuming a build can use both, pom.xml files and no pom.xml files? Without complications? 

Not to mention, I hate to be the "early tester", since we have such a complicated project has it is. 

What is your assessment given those concerns? How many pom.xml files could we "get rid of" without any impact? 

I assume that is your goal; be to get rid of many pom.xml files, and therefore, have less maintenance to do later?
Comment 4 Lars Vogel CLA 2015-12-02 09:57:54 EST
(In reply to David Williams from comment #3)
> I have reservations about using "pom-less builds". 
> 
> What problem is it solving, for us? 

Less maintenance.

> I am assuming there is no way we could ever go completely pom-less, so it
> does not seem like too much of an enhancement, and might just be more
> confusing. 
> 
> I am assuming a build can use both, pom.xml files and no pom.xml files?
> Without complications? 

Yes. In a customer implementation we are using a mixture of no poms and with pom files. So far without problems.

> Not to mention, I hate to be the "early tester", since we have such a
> complicated project has it is. 

I move that bug to M5.

> What is your assessment given those concerns? How many pom.xml files could
> we "get rid of" without any impact? 

All plug-ins and features poms which have no special entries, like ignore generic warnings. For test plug-ins we most likely have to stay with poms, as most of them require the configuration of a test class.

> I assume that is your goal; be to get rid of many pom.xml files, and
> therefore, have less maintenance to do later?

Yes.
Comment 5 Alexander Kurtakov CLA 2018-05-30 01:39:33 EDT
I like the idea. It will reduce this crazy pom update a lot.
Comment 7 Eclipse Genie CLA 2018-06-01 06:09:29 EDT
New Gerrit change created: https://git.eclipse.org/r/123820