Re: [tycho-dev] A little status report

[Benson Margulies <bimargulies@xxxxxxxxx>]

Jan,

My general experience has been that messing with the <modules/> causes
problems. The biggest such problem is with the release plugin.

Of course, that's not a consideration for Tycho now, but it might be some day.

I'd recommend looking for another solution, and I'll let you know if I find one.

--benson


On Tue, Sep 6, 2011 at 4:32 AM, Sievers, Jan <jan.sievers@xxxxxxx> wrote:
>>versus non-public documentation. So I'm looking for a short cut. If
>>you want to keep the tree as is, I'll go figure out how to persuade
>>the site plugin to skip the integration tests and suchlike.
>
> a build profile for site generation which only lists those modules
> relevant for mvn site could help.
>
> Jan
>
> -----Original Message-----
> From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Benson Margulies
> Sent: Samstag, 3. September 2011 18:53
> To: Tycho developers list
> Subject: Re: [tycho-dev] A little status report
>
> On Sat, Sep 3, 2011 at 9:41 AM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
>> I am not familiar with site-plugin. Are you saying it cannot follow
>> nested project structure, which is very common for any real-work project
>> with 20+ modules?
>
> Yes it follows site structure. However, it's not altogether obvious
> how to make it *not* follow site structure.
>
> I don't think anyone wants to read mvn site doc for all those
> integration tests, and Jan was concerned about public documentation
> versus non-public documentation. So I'm looking for a short cut. If
> you want to keep the tree as is, I'll go figure out how to persuade
> the site plugin to skip the integration tests and suchlike.
>
>
>>
>> --
>> Regards,
>> Igor
>>
>> On 11-09-03 9:16 AM, Benson Margulies wrote:
>>>
>>> On Sat, Sep 3, 2011 at 9:12 AM, Igor Fedorenko<igor@xxxxxxxxxxxxxx>
>>>  wrote:
>>>>
>>>> I'd rather keep plugins grouped by their logical components, as they are
>>>> today. For example, all code related to testing currently lives under
>>>> tycho-surefire folder, which makes it easier to both see the code
>>>> together and to rebuild just the testing support. This also provides
>>>> natural place where to split the code to separate git repositories, when
>>>> we decide to do so.
>>>
>>> My real goal here is to have one place to run 'mvn site' that will
>>> build a multi-module site of the public side of tycho. Is there a way
>>> to do this compatible with the above? If not, then the next best thing
>>> is to set up the sites of all the public components to be relatively
>>> independent of each other.
>>>
>>>
>>>>
>>>> --
>>>> Regards,
>>>> Igor
>>>>
>>>> On 11-09-02 7:35 PM, Benson Margulies wrote:
>>>>>
>>>>> The problem with the tycho-maven-plugin is fixed in
>>>>> maven-plugin-plugin version 2.9, currently being voted on at Maven.
>>>>>
>>>>> I have a little proposal. Move all the actual documentable plugins
>>>>> under one directory. Then we can run mvn site and publish from there,
>>>>> and not spend time on the integration tests.
>>>>> _______________________________________________
>>>>> tycho-dev mailing list
>>>>> tycho-dev@xxxxxxxxxxx
>>>>> https://dev.eclipse.org/mailman/listinfo/tycho-dev
>>>>
>>>> _______________________________________________
>>>> tycho-dev mailing list
>>>> tycho-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/tycho-dev
>>>>
>>> _______________________________________________
>>> tycho-dev mailing list
>>> tycho-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/tycho-dev
>>
>> _______________________________________________
>> tycho-dev mailing list
>> tycho-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/tycho-dev
>>
> _______________________________________________
> tycho-dev mailing list
> tycho-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-dev
> _______________________________________________
> tycho-dev mailing list
> tycho-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-dev
>