Mailing-List: contact click-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: click-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of sabob1@gmail.com designates
 209.85.160.41 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=ifRs/WujZv1MKPlbFM+SYfj+m49m/HuPnvN3A+dSMEry0jG4eE+MVFiB7wVmV9Xjun
         W+v7ZNy1o8WrgZIctrF2VWEualIOUKqfqaJu1aSfap7Soe9M/cukjrMdX8kBak2I0RYY
         p7pP/0EaZq6uDTlMkU05PaJkmLcH3Oa2WWuy4=
Message-ID: <4B544F2C.9000402@gmail.com>
Date: Mon, 18 Jan 2010 23:08:12 +1100
From: Bob Schellink <sabob1@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0
MIME-Version: 1.0
To: click-dev@incubator.apache.org
Subject: Re: Next release of ClickIDE
References: <285ca09a1001170846t4a035799ka4f9de10b4ab7dbd@mail.gmail.com>
	 <4B538765.2010609@gmail.com>
 <285ca09a1001180355x393327fdn48dba87e5e1d407e@mail.gmail.com>
In-Reply-To: <285ca09a1001180355x393327fdn48dba87e5e1d407e@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Naoki,

I assume creating an Eclipse plugin is done through the IDE itself? In the README.txt could you 
provide a brief description of how to do this? I tried briefly to build the plugin but don't 
understand enough of Eclipse plugin development.

kind regards

bob

On 18/01/2010 10:55 PM, Naoki Takezoe wrote:
> Hi Bob,
>
> Thanks for your advice.
>
> I will make README.txt referring to Click's README.
>
> I'll also extract files which don't suit Apache License 2.0
> and don't have Apache legal requirements.
>
> Regards,
>
> 2010/1/18 Bob Schellink<sabob1@gmail.com>:
>> Hi Naoki,
>>
>> Yes, we haven't had a release of Click and ClickIDE in a long time. We only
>> have one remaining hurdle though which is the migration of Click
>> infrastucture to a TLP:
>>
>> https://issues.apache.org/jira/browse/INFRA-2425
>>
>> Once the above issues have been resolved we can push out Click 2.1.0 as a
>> TLP.
>>
>> For ClickIDE we will need to go through the codebase and check that we meet
>> Apache legal requirements. For example, what is the license of the icons?
>> Are there any code in ClickIDE that is under a different license from Apache
>> License 2.0? Perhaps a third-party library? We will need to list that in a
>> LICENSE.txt and NOTICE.txt file. (I will help with this).
>>
>> I checked out the project from [1] but cannot find how to build and run the
>> IDE from source. There are three subprojects under the eclipse folder.
>> Should we import only the root folder or each subproject individually? Would
>> you mind adding a README.txt to the ClickIDE project outlining how to build
>> and run the project from source? You could use Click's README [2] as an
>> example.
>>
>> kind regards
>>
>> bob
>>
>> [1]: http://svn.apache.org/viewvc/incubator/click/trunk/tools/eclipse/
>> [2]:
>> http://svn.apache.org/viewvc/incubator/click/trunk/click/README.txt?view=markup
>>
>>
>> On 18/01/2010 03:46 AM, Naoki Takezoe wrote:
>>>
>>> Hi,
>>>
>>> The next version of ClickIDE that supports Click 2.1.0 and
>>> Eclipse 3.5 is ready. However Click 2.1.0 is still release candidate.
>>> So ClickIDE in the SVN trunk contains Click 2.1.0 RC1 JARs.
>>>
>>> I wish to release ClickIDE in the near future because ClickIDE
>>> has not been upgraded for a long term.
>>>
>>> What should I plan the future release of ClickIDE...?
>>>
>>> Regards,
>>>
>>
>>
>
>
>