You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "David Savage (JIRA)" <ji...@apache.org> on 2009/07/13 19:11:14 UTC
[jira] Created: (FELIX-1326) Refactor package names in code to
org.apache.felix.sigil
Refactor package names in code to org.apache.felix.sigil
--------------------------------------------------------
Key: FELIX-1326
URL: https://issues.apache.org/jira/browse/FELIX-1326
Project: Felix
Issue Type: Task
Components: Sigil
Reporter: David Savage
Priority: Critical
currently package names are org.cauldron.*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1326) Refactor package names in code to
org.apache.felix.sigil
Posted by "David Savage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Savage updated FELIX-1326:
--------------------------------
Fix Version/s: sigil-0.1.0
set release version
> Refactor package names in code to org.apache.felix.sigil
> --------------------------------------------------------
>
> Key: FELIX-1326
> URL: https://issues.apache.org/jira/browse/FELIX-1326
> Project: Felix
> Issue Type: Task
> Components: Sigil
> Reporter: David Savage
> Assignee: David Savage
> Priority: Critical
> Fix For: sigil-0.1.0
>
>
> currently package names are org.cauldron.*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1326) Refactor package names in code to
org.apache.felix.sigil
Posted by "David Savage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Savage closed FELIX-1326.
-------------------------------
> Refactor package names in code to org.apache.felix.sigil
> --------------------------------------------------------
>
> Key: FELIX-1326
> URL: https://issues.apache.org/jira/browse/FELIX-1326
> Project: Felix
> Issue Type: Task
> Components: Sigil
> Reporter: David Savage
> Assignee: David Savage
> Priority: Critical
> Fix For: sigil-0.1.0
>
>
> currently package names are org.cauldron.*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-1326) Refactor package names in code to
org.apache.felix.sigil
Posted by "David Savage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Savage reassigned FELIX-1326:
-----------------------------------
Assignee: David Savage
> Refactor package names in code to org.apache.felix.sigil
> --------------------------------------------------------
>
> Key: FELIX-1326
> URL: https://issues.apache.org/jira/browse/FELIX-1326
> Project: Felix
> Issue Type: Task
> Components: Sigil
> Reporter: David Savage
> Assignee: David Savage
> Priority: Critical
>
> currently package names are org.cauldron.*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Resolved: (FELIX-1326) Refactor package names in code
to org.apache.felix.sigil
Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 7/14/09 12:23 PM, David Savage wrote:
> Ok, makes sense. I'll do that - I guess I have priviledges to set up
> versions in the felix jira? I'll try and bounce back if I can't...
>
> As an aside I was planning to try to build sigil with sigil vs via maven:
>
> https://issues.apache.org/jira/browse/FELIX-1323
>
> This would make it a good test scenario for OSGi development e.g. eat
> our own dog food. Of course this would then mean it would have a
> different build to the rest of felix which is maven based.
> Alternatively I could try to build a maven build for sigil but I've
> not tried this before and I get the feeling I might run into similar
> problems that are being discussed on the user list at the moment:
>
> http://www.mail-archive.com/users@felix.apache.org/msg05017.html
>
> Seems sensible to raise this early before doing a lot of work that
> might head us off in the wrong direction...
>
I don't have an issue with Sigil building Sigil.
-> richard
> Regards,
>
> Dave
>
> On Tue, Jul 14, 2009 at 5:09 PM, Richard S. Hall<he...@ungoverned.org> wrote:
>
>> Typically, we have trunk working on an odd numbered minor release as the
>> development version and then release an even numbered version. So, perhaps
>> Sigil should be 0.9.0-SNAPSHOT in trunk, working toward 1.0.0 (or 0.10.0 or
>> whatever even number you want). This approach makes like a little better
>> with Maven and OSGi since 1.0.0-SNAPSHOT is less than 1.0.0 in Maven, but
>> not in OSGi.
>>
>> -> richard
>>
>> On 7/14/09 12:03 PM, David Savage (JIRA) wrote:
>>
>>> [
>>> https://issues.apache.org/jira/browse/FELIX-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>> ]
>>>
>>> David Savage resolved FELIX-1326.
>>> ---------------------------------
>>>
>>> Resolution: Fixed
>>>
>>> relevant patches applied to svn.
>>>
>>> Not currently targetted at a release. Wondering what this should be? I
>>> guess current effort is to head towards a 1.0 of sigil on felix?
>>>
>>>
>>>
>>>> Refactor package names in code to org.apache.felix.sigil
>>>> --------------------------------------------------------
>>>>
>>>> Key: FELIX-1326
>>>> URL: https://issues.apache.org/jira/browse/FELIX-1326
>>>> Project: Felix
>>>> Issue Type: Task
>>>> Components: Sigil
>>>> Reporter: David Savage
>>>> Assignee: David Savage
>>>> Priority: Critical
>>>>
>>>> currently package names are org.cauldron.*
>>>>
>>>>
>>>
>
>
>
>
Re: [jira] Resolved: (FELIX-1326) Refactor package names in code to
org.apache.felix.sigil
Posted by David Savage <da...@paremus.com>.
Ok, makes sense. I'll do that - I guess I have priviledges to set up
versions in the felix jira? I'll try and bounce back if I can't...
As an aside I was planning to try to build sigil with sigil vs via maven:
https://issues.apache.org/jira/browse/FELIX-1323
This would make it a good test scenario for OSGi development e.g. eat
our own dog food. Of course this would then mean it would have a
different build to the rest of felix which is maven based.
Alternatively I could try to build a maven build for sigil but I've
not tried this before and I get the feeling I might run into similar
problems that are being discussed on the user list at the moment:
http://www.mail-archive.com/users@felix.apache.org/msg05017.html
Seems sensible to raise this early before doing a lot of work that
might head us off in the wrong direction...
Regards,
Dave
On Tue, Jul 14, 2009 at 5:09 PM, Richard S. Hall<he...@ungoverned.org> wrote:
> Typically, we have trunk working on an odd numbered minor release as the
> development version and then release an even numbered version. So, perhaps
> Sigil should be 0.9.0-SNAPSHOT in trunk, working toward 1.0.0 (or 0.10.0 or
> whatever even number you want). This approach makes like a little better
> with Maven and OSGi since 1.0.0-SNAPSHOT is less than 1.0.0 in Maven, but
> not in OSGi.
>
> -> richard
>
> On 7/14/09 12:03 PM, David Savage (JIRA) wrote:
>>
>> [
>> https://issues.apache.org/jira/browse/FELIX-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> David Savage resolved FELIX-1326.
>> ---------------------------------
>>
>> Resolution: Fixed
>>
>> relevant patches applied to svn.
>>
>> Not currently targetted at a release. Wondering what this should be? I
>> guess current effort is to head towards a 1.0 of sigil on felix?
>>
>>
>>>
>>> Refactor package names in code to org.apache.felix.sigil
>>> --------------------------------------------------------
>>>
>>> Key: FELIX-1326
>>> URL: https://issues.apache.org/jira/browse/FELIX-1326
>>> Project: Felix
>>> Issue Type: Task
>>> Components: Sigil
>>> Reporter: David Savage
>>> Assignee: David Savage
>>> Priority: Critical
>>>
>>> currently package names are org.cauldron.*
>>>
>>
>>
>
--
-------------------------------------------------------------------------------------
Paremus Limited. Registered in England. Registration No. 4181472
Registered Office: 22-24 Broad Street, Wokingham, Berks RG40 1BA
Postal Address: 107-111 Fleet Street, London, EC4A 2AB
The information transmitted is intended only for the person(s) or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or
other use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended recipient
is prohibited.
If you received this in error, please contact the sender and delete
the material from any computer.
-------------------------------------------------------------------------------------
Re: [jira] Resolved: (FELIX-1326) Refactor package names in code
to org.apache.felix.sigil
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Typically, we have trunk working on an odd numbered minor release as the
development version and then release an even numbered version. So,
perhaps Sigil should be 0.9.0-SNAPSHOT in trunk, working toward 1.0.0
(or 0.10.0 or whatever even number you want). This approach makes like a
little better with Maven and OSGi since 1.0.0-SNAPSHOT is less than
1.0.0 in Maven, but not in OSGi.
-> richard
On 7/14/09 12:03 PM, David Savage (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/FELIX-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> David Savage resolved FELIX-1326.
> ---------------------------------
>
> Resolution: Fixed
>
> relevant patches applied to svn.
>
> Not currently targetted at a release. Wondering what this should be? I guess current effort is to head towards a 1.0 of sigil on felix?
>
>
>> Refactor package names in code to org.apache.felix.sigil
>> --------------------------------------------------------
>>
>> Key: FELIX-1326
>> URL: https://issues.apache.org/jira/browse/FELIX-1326
>> Project: Felix
>> Issue Type: Task
>> Components: Sigil
>> Reporter: David Savage
>> Assignee: David Savage
>> Priority: Critical
>>
>> currently package names are org.cauldron.*
>>
>
>
[jira] Resolved: (FELIX-1326) Refactor package names in code to
org.apache.felix.sigil
Posted by "David Savage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Savage resolved FELIX-1326.
---------------------------------
Resolution: Fixed
relevant patches applied to svn.
Not currently targetted at a release. Wondering what this should be? I guess current effort is to head towards a 1.0 of sigil on felix?
> Refactor package names in code to org.apache.felix.sigil
> --------------------------------------------------------
>
> Key: FELIX-1326
> URL: https://issues.apache.org/jira/browse/FELIX-1326
> Project: Felix
> Issue Type: Task
> Components: Sigil
> Reporter: David Savage
> Assignee: David Savage
> Priority: Critical
>
> currently package names are org.cauldron.*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.