click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Schellink (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CLKE-36) Ensure ClickIDE source code meets Apache legal requirements
Date Wed, 20 Jan 2010 11:26:54 GMT

    [ https://issues.apache.org/jira/browse/CLKE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802794#action_12802794
] 

Bob Schellink commented on CLKE-36:
-----------------------------------

Sorry to be such a pain but another requirement is for us to ship a zip file containing the
source code. With Click itself we ship a single zip containing both the source+binaries. Should
we do the same with ClickIDE or have a separate zip file for the sources?

Btw I'm using Velocity Tools as an example of how to distribute an Apache subproject. Here
is how Velocity Tools packages their distributions: http://velocity.apache.org/download.cgi

We also need to include the LICENSE.txt and NOTICE.txt in our jars under the folder META-INF.
Not sure if Eclipse Export Wizard is flexible enough to do this?

Is it possible to build ClickIDE from standalone ant? That will make it easier to assemble
a proper build.

> Ensure ClickIDE source code meets Apache legal requirements
> -----------------------------------------------------------
>
>                 Key: CLKE-36
>                 URL: https://issues.apache.org/jira/browse/CLKE-36
>             Project: Click Eclipse
>          Issue Type: Task
>    Affects Versions: 2.1.0
>            Reporter: Bob Schellink
>            Assignee: Naoki Takezoe
>            Priority: Blocker
>             Fix For: 2.1.0.0
>
>         Attachments: clickide.txt
>
>
> We need to ensure that ClickIDE meets all the legal requirements of an Apache release.
> Attached is the RAT[1] report which lists file with missing license headers. We're in
pretty good shape. The files below needs a license though:
> clickide-svn/eclipse/org.apache.click.eclipse/schema/configurationProvider.exsd
> clickide-svn/eclipse/org.apache.click.eclipse/build.properties
> clickide-svn/eclipse/org.apache.click.eclipse/memo.txt
> clickide-svn/eclipse/org.apache.click.eclipse/META-INF/MANIFEST.MF
> clickide-svn/eclipse/org.apache.click.eclipse.cayenne/build.properties
> clickide-svn/eclipse/org.apache.click.eclipse.cayenne/META-INF/MANIFEST.MF
> clickide-svn/eclipse/org.apache.click.eclipse.cayenne/src/org/apache/click/eclipse/cayenne/CayenneClasspathContainerInitializer.java
> clickide-svn/eclipse/org.apache.click.eclipse.cayenne/src/org/apache/click/eclipse/cayenne/CayenneClasspathContainerPage.java
> clickide-svn/eclipse/org.apache.click.eclipse.cayenne/src/org/apache/click/eclipse/cayenne/messages.properties
> clickide-svn/eclipse/org.apache.click.eclipse.cayenne/src/org/apache/click/eclipse/cayenne/messages_ja.properties
> clickide-svn/eclipse/org.apache.click.eclipse.cayenne/src/org/apache/click/eclipse/cayenne/wizard/cayenne.xml
> clickide-svn/eclipse/org.apache.click.eclipse.feature/build.properties
> We need a NOTICE.txt, LICENSE.txt and README.txt in the source root folder.
> We need to determine where the icons were sourced from.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message