On 28 June 2011 15:40, Benson Margulies wrote:
> Sebb,
>
> I think that you are pointing at the dilemma at the center of this.
>
> Anything like this that we put into the top pom is inherited unless
> overriden, and people are skittish about accidently making everything
> part of the Maven project
done [1]
site deployed [2]
any comments appreciated to continue to improve the documentation
Regards,
Hervé
[1] http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?view=markup
[2] http://maven.apache.org/pom/asf/
Le mardi 28 juin 2011, sebb a écrit :
> May I make a plea for the ASF POM
Sebb,
I think that you are pointing at the dilemma at the center of this.
Anything like this that we put into the top pom is inherited unless
overriden, and people are skittish about accidently making everything
part of the Maven project.
Where would you propose that we put a link to that it wou
May I make a plea for the ASF POM to include a link to the
documentation in the comments?
Also, maybe someone can fix the very long comment line starting with:
"As of Version 6, "
The description could be wrapped as well.
On 27 June 2011 21:42, Benson Margulies wrote:
> It occurs to me that th
It occurs to me that the main pom could include a profile to run the
site pom via the invoker.
On Mon, Jun 27, 2011 at 4:36 PM, Hervé BOUTEMY wrote:
> option 1 seems to be controversial
>
> option 2, with site-pom.xml as suggested by Jörg, with specific siteDirectory
> site plugin configuration (
None here.
On Mon, Jun 27, 2011 at 4:36 PM, Hervé BOUTEMY wrote:
> option 1 seems to be controversial
>
> option 2, with site-pom.xml as suggested by Jörg, with specific siteDirectory
> site plugin configuration (to avoid site.xml problem like pom.xml), seems
> pretty good
>
> option 3, [1], does
option 1 seems to be controversial
option 2, with site-pom.xml as suggested by Jörg, with specific siteDirectory
site plugin configuration (to avoid site.xml problem like pom.xml), seems
pretty good
option 3, [1], doesn't seem accessible in the short term
any objection to go with option 2?
Re
OK, call that '2(c)' from my list.
On Mon, Jun 27, 2011 at 3:07 AM, Jörg Schaible
wrote:
> Hi Hervé,
>
> Hervé BOUTEMY wrote:
>
>>> Now the question is: where do we put ASF pom documentation?
>> sharing a few thoughts:
>> 1. in the project itself? need to find a way to get its publication done
>>
Hi Hervé,
Hervé BOUTEMY wrote:
>> Now the question is: where do we put ASF pom documentation?
> sharing a few thoughts:
> 1. in the project itself? need to find a way to get its publication done
> without tainting the pom
Just an idea: Use a separate pom file with the proper site settings in the
Option 1: go ahead and put a full configuration in this POM, and then
make sure that all of the things that use it really do over-ride it.
Option 2: Give it a parent or child: create a project with a site just
to document and aggregate this, with enough SEO to catch googles.
Option 3: take up my
> Now the question is: where do we put ASF pom documentation?
sharing a few thoughts:
1. in the project itself? need to find a way to get its publication done
without tainting the pom
2. in the Maven site [1], in a dedicated directory
3. at the top of pom svn [2]: the main difference I see from
11 matches
Mail list logo