Re: [eclipse.org-planning-council] about.html requirements

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

Wayne,

We discussed on rt-pmc and came up with a couple of options, is there
a way we could get a ruling on this so I could make the change for our
next release?

The preferred option would be to add a new manifest entry called
something like ECLIPSE_ABOUT_FILE that had a default location of
simply /about.html but that this header could be used by any project
that was looking for doing something with these files to locate the
about.html file should that property be defined.  This way we could
set it for our artifacts as needed.  If it was not set it then the
assumption is its /about.html and is exactly what all the other
projects are doing right now anyway.

[default]
ECLIPSE_ABOUT_FILE /about.html

[under meta-inf]
ECLIPSE_ABOUT_FILE /META-INF/about.html

[differently named]
ECLIPSE_ABOUT_FILE /jetty-server-about.html

This would give all the flexibility needed to ensure the about.html
file existed and allow whoever is using these files for their own
purposes a mechanism to locate it should it not be in the root named
about.html.

Thoughts?

jesse


--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx


On Tue, May 29, 2012 at 10:30 AM, Jesse McConnell
<jesse.mcconnell@xxxxxxxxx> wrote:
> correct
>
> and perhaps its better to say that its when it is all pulled together
> into the final artifact, i would assume the manifest is undergoing
> some sort of merge but my understanding is that assembly issue is
> where the about.html thing comes from
>
> jesse
>
> --
> jesse mcconnell
> jesse.mcconnell@xxxxxxxxx
>
>
> On Tue, May 29, 2012 at 10:21 AM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
>> So Manifest.MF is not subject to the unique files across the JARs issue?
>>
>> Wayne
>>
>>
>> On 05/29/2012 11:19 AM, Jesse McConnell wrote:
>>
>> off the top of my head....so much else is communicated and managed
>> through the MANIFEST.MF file, why not just have a name/value pair in
>> there that provides the relevant information, or a link to a page
>> detailing that relevant information?
>>
>> I'll mention it in the rt-pmc call tomorrow, thanks
>>
>> jesse
>>
>>
>> --
>> jesse mcconnell
>> jesse.mcconnell@xxxxxxxxx
>>
>>
>> On Tue, May 29, 2012 at 10:10 AM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
>>
>> For starters...
>>
>> When compiling for android devices, dalvik requires that there be
>> unique files across the jars
>>
>> Really?! This seems odd/strange. I assume that it applies to manifest,
>> configuration files, images, etc. Seems limiting, but I guess that size is
>> an important consideration on devices (or is there some other technical
>> reason).
>>
>> The about.html is a convenient means to enforce the IP Policy [1]:
>>
>> Before any Content is placed in the Repository or made available for
>> download or other
>> method of distribution, the applicable Committer(s) must ensure that the
>> terms and
>> conditions governing the subsequent use of the Content are clearly
>> communicated to
>> potential recipients of the Content.
>>
>> The wording in the Guide to the Legal Documentation for Eclipse-Based
>> Content [2] notwithstanding, we have some wiggle room here. Starting from an
>> assumption that we must ensure that the terms are communicated, what do you
>> recommend we do?
>>
>> This seems like it might be a general runtime issue that might be a good
>> topic for discussion by the RT PMC.
>>
>> Wayne
>>
>> [1] http://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf
>> [2] http://www.eclipse.org/legal/guidetolegaldoc.php
>>
>>
>> On 05/29/2012 08:45 AM, Jesse McConnell wrote:
>>
>> I just got a reminder on our users list about the pain this about.html
>> file requirement causes some of our users.  I am bringing this up
>> because I have seen the about.html file requirement crop up on the
>> juno threads.
>>
>> When compiling for android devices, dalvik requires that there be
>> unique files across the jars and when you start pulling in a couple of
>> eclipse jetty jar files with those about.html files it breaks their
>> build.  To combat that some of our users have had to resort to
>> cracking open our jars and removing that about.html file.  We do
>> distribute an aggregate source jar that can work in most instances (I
>> believe) but using the aggregates is not typically where people start
>> out and this is a poor user experience.
>>
>> (and yes, jetty does run on android phones :)
>>
>> So I am curious, how firm is this about.html file requirement and does
>> it make sense anymore in today's day and age?
>>
>> jesse
>>
>> --
>> jesse mcconnell
>> jesse.mcconnell@xxxxxxxxx
>> _______________________________________________
>> eclipse.org-planning-council mailing list
>> eclipse.org-planning-council@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
>>
>> IMPORTANT: Membership in this list is generated by processes internal to the
>> Eclipse Foundation.  To be permanently removed from this list, you must
>> contact emo@xxxxxxxxxxx to request removal.
>>
>>
>> --
>> Wayne Beaton
>> The Eclipse Foundation
>> Twitter: @waynebeaton
>> Explore Eclipse Projects
>>
>> _______________________________________________
>> eclipse.org-planning-council mailing list
>> eclipse.org-planning-council@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
>>
>> IMPORTANT: Membership in this list is generated by processes internal to the
>> Eclipse Foundation.  To be permanently removed from this list, you must
>> contact emo@xxxxxxxxxxx to request removal.
>>
>> _______________________________________________
>> eclipse.org-planning-council mailing list
>> eclipse.org-planning-council@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
>>
>> IMPORTANT: Membership in this list is generated by processes internal to the
>> Eclipse Foundation.  To be permanently removed from this list, you must
>> contact emo@xxxxxxxxxxx to request removal.
>>
>>
>> --
>> Wayne Beaton
>> The Eclipse Foundation
>> Twitter: @waynebeaton
>> Explore Eclipse Projects
>>
>> _______________________________________________
>> eclipse.org-planning-council mailing list
>> eclipse.org-planning-council@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
>>
>> IMPORTANT: Membership in this list is generated by processes internal to the
>> Eclipse Foundation.  To be permanently removed from this list, you must
>> contact emo@xxxxxxxxxxx to request removal.