[jbosstools-dev] Who uses .target file?

[Nick Boldt]

On 03/14/2012 12:41 PM, Max Rydahl Andersen wrote:
>
> Noone uses it right now since it is not set up as it should be afaik
>
> I would/want to use it if we enable slide planner mode on it so the dependencies becomes *deterministic*. They aren't now.

Depends on what you mean by deterministic. Currently, the script that 
allows you to turn a .target file into an update site can run in two modes:

* useLatest=true (get whatever versions of the listed IUs are available 
on the upstream sites) and
* useLatest=false (use exactly the versions of IUs listed in the .target 
file)

Does that not meet both the need to resolve a TP on disk from the 
explicit versions listed, or to update it from the latest in the 
requirements mirror? (eg., when it's time to move from SR1 to SR2)

> And then I would like to get target files that I can apply in eclipse - but the current one is just too big/slow to work.

How would you propose bifurcating them? What features would be in what 
chunks? Maven bucket? SOA bucket? Teiid bucket? Need some idea how to 
break this into smaller pieces.

Please provide suggestions as subtasks of JBIDE-10915, eg, "create a 
target platform & site containing only the following features: 
a.feature, b.feature, c.feature...".

> Using an updatesite would not help on that either afaik.

An update site w/ all the featureless plugins referenced by a top-level 
feature which would provide a way to easily install the whole site into 
your Eclipse either by hand or via p2.director script? Yes, yes it would.

> /max
>
> On Mar 14, 2012, at 3:55 PM, Mickael Istria wrote:
>
>> Hi all,
>>
>> This is an important question for us.
>> Nick and I are now convinced that .target files are not the panacea to drive dependency management at build time. It adds a lot of additional steps and it does not work that easily in the Maven way. We are thinking of some alternatives way to provide a "dependency" repository that would contain only the necessary stuff for you to work on your component. Then we'll just manage this repository instead of a .target file, it should make our daily work better and remove lot of complexity.
>> See https://issues.jboss.org/browse/JBIDE-10915 and comments starting from here https://issues.jboss.org/browse/JBIDE-11157?focusedCommentId=12676643&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12676643 for more details/debate.
>>
>> So we more and more think this .target file is useless, and we'd like to get rid of it (uselessness is bad). But before that, we'd like to know whether some of you do use the generated .target file. If yes, we'll have to think on a better way to make everyone happy. So if you use .target file, raise your hand!
>> --
>> Mickael Istria
>> Eclipse developer at JBoss, by Red Hat
>> My blog - My Tweets
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com