[jbosstools-dev] Who uses .target file?

[Nick Boldt]

Right, I forget you're downstream from JBoss Tools Core. This usecase is 
being considered here:

https://issues.jboss.org/browse/JBIDE-10915?focusedCommentId=12676765&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12676765

We also provide bootstrap profiles [0] for building JBT components (and 
their upstream bits) but that's a bit harder to do when your stuff's in 
github and the rest is elsewhere. That's useful when you need to rebuild 
upstream stuff, but not as useful when you just want to resolve against 
upstream binaries.

[0] 
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/pom-soa-tooling.xml

For resolving against upstream binaries, we provide these sites [1], 
[2], but having them merged into a single TP would certainly be simpler.

[1] http://download.jboss.org/jbosstools/updates/indigo/ (requirements)
[2] http://download.jboss.org/jbosstools/updates/development/indigo/ 
(JBT Core)

(And of course there are nightly versions if you want something more 
bleeding edge.)


On 03/14/2012 01:47 PM, Rob Cernich wrote:
> Sorry.  Let me clarify, when I say target platform, I would also include the JBoss plugins.  Having an all inclusive target file allows me to checkout a specific project and work on it, without having to root out the specific project dependencies, which then means either installing them into a local target platform or checking out their source, then repeating for any missing dependencies of the dependencies, and so on.  I may end up having to checkout half of JBT (or installing everything into a local target) just to work on a simple, segregated feature.  At least having a target file automates the process (even if it does take a while to download everything).
>
> ----- Original Message -----
>>
>>
>> On 03/14/2012 01:21 PM, 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.
>>
>> Target Platform exists as a zip and an exploded site:
>> http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.SR2/
>> (for building anything in JBoss Tools Core -- download the zip,
>> unpack
>> it, and use it thus: `mvn clean install
>> -Dlocal.site=file:///path/to/unzipped/site/ -Plocal.site` or use that
>> site to install into your Eclipse for use w/ PDE)
>>
>> It's also a unified.target file if you prefer:
>>
>> http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/
>>
>> Tests: https://issues.jboss.org/browse/JBIDE-11077 (coming soon)
>>
>>> 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.
>>
>> *cough* http://eclipsesource.com/en/yoxos/ ? */cough*
>>
>> (latest Yoxos 5.5 includes Eclipse 3.7.2:
>> http://eclipsesource.com/blogs/2012/02/26/yoxos-5-5-and-eclipse-3-7-2/)
>>
>>>
>>> ----- 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
>>>>
>>>
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools&  Dev Studio
>> http://nick.divbyzero.com
>>

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