[jbosstools-dev] Who uses .target file?

[Denis Golovin]

+1 to keep .target files.

That's what we use here in concord.

We have Development Target Platform which includes SDK's that match 
Runtime Target Platform components. Target file is used in two ways 
here: to build it and to enable it in target platform (haven't committed 
yet in my workspace, but should be there in couple days).

The flow is:
1. Download Eclipse SDK, install Subversion Integration (WTP XML 
editing, M2E and etc);
2. Checkout Dev TP into workspace;
3. Run maven clean install;
4. Open .target file and click use it as Target Platform in upper right 
corner;
5. Checkout or import (it is up to developer which way to go) component 
plugins;;
6. Build, rebuild and run without worries that you missed dependencies;

What is good in this:
1. You have in minimal configuration SDK and SVN only in your dev 
environment and it means your menus, preferences is not clattered with 
all none relevant for eclipse development items in 
menus/toolbars/preferences.
2. update to new version is easy, just update Dev TP, rebuild it and 
refresh TP in Eclipse
3. you have sources for debugging for every dependency

Now I am thinking about replacing step 1 with maven, so maven would be 
single entry point to build Dev Environment and target platform, then 
developer should just start built development  environment, import TP 
into workspace, set .target file as cirrent target platform, export 
sources and start working.

Denis




On 03/14/2012 10:21 AM, Rob Cernich wrote:
> I agree with Max.  It would be nice if a target file were available.  Right now, the developer must manage his own target platform.  This is compounded by the fact that the base "test" plugins are not available directly from a p2 repository (update site) and must be downloaded and installed separately.
>
> As far as the slowness, I believe you only pay that when you setup or update your target platform (as the new dependencies are downloaded and updated).  Same price you pay when updating your local target platform.
>
> This would be a really nice feature as it makes it easy to setup a development workspace; saves you from having to find all the dependencies yourself.
>
> ----- Original Message -----
>> 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.
>>
>> 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.
>>
>> Using an updatesite would not help on that either afaik.
>>
>> /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
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev