click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naoki Takezoe (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CLKE-36) Ensure ClickIDE source code meets Apache legal requirements
Date Thu, 21 Jan 2010 17:15:54 GMT

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

Naoki Takezoe commented on CLKE-36:
-----------------------------------

Hi Bob,

I moved LICENSE.txt and NOTICE.txt to META-INF. Each plugin jar files would contain them in
META-INF.
And put README.txt, LICENSE.txt and NOTICE.txt to the parent eclipse directory.

I think we can provide a source zip file of ClickIDE by zipping eclipse directory (parent
directory of plugin projects).

> Is it possible to build ClickIDE from standalone ant?

It's very difficult. It's possible to build plugins using Ant, however it requires Eclipse
headless run on the 
build environment. But it's not realistic. Actually, we would have to build ClickIDE manually
for release.

> 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