You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by "Andrus Adamchik (JIRA)" <de...@cayenne.apache.org> on 2007/10/25 19:50:51 UTC
[JIRA] Created: (CAY-904) Switch cayenne to Java 5: merge
cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished
Switch cayenne to Java 5: merge cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished
----------------------------------------------------------------------------------------
Key: CAY-904
URL: https://issues.apache.org/cayenne/browse/CAY-904
Project: Cayenne
Issue Type: Task
Components: Cayenne Core Library
Affects Versions: 3.0
Reporter: Andrus Adamchik
Assignee: Andrus Adamchik
Fix For: 3.0
merge cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished , edit parent poms and assemblies.
Do not get rid of cayenne-jdk1.5-unpublished, as we may have to maintain the split JDK versions going forward when starting with 1.6 support
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [JIRA] Created: (CAY-904) Switch cayenne to Java 5: merge cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished
Posted by Andrus Adamchik <an...@objectstyle.org>.
Starting that now. Stay tuned.
On Nov 14, 2007, at 9:42 AM, Kevin Menard wrote:
> +1.
>
> I should be able to carry my changes over fairly easily. They're
> mostly
> Velocity template changes at the moment.
>
> I especially agree with documenting items as we make them generic.
> There's
> a lot of Object accesses that are a bit confusing in the code.
>
> --
> Kevin
>
>
> On 11/13/07 6:09 PM, "Aristedes Maniatis" <ar...@ish.com.au> wrote:
>
>>
>> On 14/11/2007, at 8:12 AM, Andrus Adamchik wrote:
>>
>>> So I guess we are now in a good shape to proceed with the switch.
>>> Any objections to me doing it sometime between tomorrow and
>>> Saturday?
>>
>> For me it is a good time. I've only got about a dozen uncommitted
>> changes right now and they should be trivial to move across. Kevin
>> might have a bigger set of patches for his work on ROP, but I'm sure
>> they will be easy to move into a different folder.
>>
>> I guess we should each pitch in as time permits to implement generics
>> in the code where the way to do so is obvious. From experience on my
>> own project this is a good time to also add javadocs which describe
>> what those lists and maps actually represent throughout the code.
>
>
>
>
Re: [JIRA] Created: (CAY-904) Switch cayenne to Java 5: merge
cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished
Posted by Kevin Menard <km...@servprise.com>.
+1.
I should be able to carry my changes over fairly easily. They're mostly
Velocity template changes at the moment.
I especially agree with documenting items as we make them generic. There's
a lot of Object accesses that are a bit confusing in the code.
--
Kevin
On 11/13/07 6:09 PM, "Aristedes Maniatis" <ar...@ish.com.au> wrote:
>
> On 14/11/2007, at 8:12 AM, Andrus Adamchik wrote:
>
>> So I guess we are now in a good shape to proceed with the switch.
>> Any objections to me doing it sometime between tomorrow and Saturday?
>
> For me it is a good time. I've only got about a dozen uncommitted
> changes right now and they should be trivial to move across. Kevin
> might have a bigger set of patches for his work on ROP, but I'm sure
> they will be easy to move into a different folder.
>
> I guess we should each pitch in as time permits to implement generics
> in the code where the way to do so is obvious. From experience on my
> own project this is a good time to also add javadocs which describe
> what those lists and maps actually represent throughout the code.
Re: [JIRA] Created: (CAY-904) Switch cayenne to Java 5: merge cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished
Posted by Aristedes Maniatis <ar...@ish.com.au>.
On 14/11/2007, at 8:12 AM, Andrus Adamchik wrote:
> So I guess we are now in a good shape to proceed with the switch.
> Any objections to me doing it sometime between tomorrow and Saturday?
For me it is a good time. I've only got about a dozen uncommitted
changes right now and they should be trivial to move across. Kevin
might have a bigger set of patches for his work on ROP, but I'm sure
they will be easy to move into a different folder.
I guess we should each pitch in as time permits to implement generics
in the code where the way to do so is obvious. From experience on my
own project this is a good time to also add javadocs which describe
what those lists and maps actually represent throughout the code.
Ari Maniatis
-------------------------->
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001 fax +61 2 9550 4001
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: [JIRA] Created: (CAY-904) Switch cayenne to Java 5: merge cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished
Posted by Andrus Adamchik <an...@objectstyle.org>.
So I guess we are now in a good shape to proceed with the switch. Any
objections to me doing it sometime between tomorrow and Saturday?
Andrus
On Oct 25, 2007, at 1:50 PM, Andrus Adamchik (JIRA) wrote:
> Switch cayenne to Java 5: merge cayenne-jdk1.4-unpublished to
> cayenne-jdk1.5-unpublished
> ----------------------------------------------------------------------
> ------------------
>
> Key: CAY-904
> URL: https://issues.apache.org/cayenne/browse/CAY-904
> Project: Cayenne
> Issue Type: Task
> Components: Cayenne Core Library
> Affects Versions: 3.0
> Reporter: Andrus Adamchik
> Assignee: Andrus Adamchik
> Fix For: 3.0
>
>
> merge cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished ,
> edit parent poms and assemblies.
>
> Do not get rid of cayenne-jdk1.5-unpublished, as we may have to
> maintain the split JDK versions going forward when starting with
> 1.6 support
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
Re: [JIRA] Closed: (CAY-904) Switch cayenne to Java 5: merge
cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished
Posted by Kevin Menard <km...@servprise.com>.
Ultimately, I think it would be nice if the entire API were parameterized
appropriately. I don't see much benefit in blocking work until that occurs
though. So, it may be worthwhile to just disable the warning in your
workspace for now and chip away at things over time.
On 11/19/07 10:31 AM, "Michael Gentry" <bl...@gmail.com> wrote:
> I apologize if this has been talked about before (I don't recall
> seeing it), but are we going to worry about Java 5/Eclipse warnings
> such as "ArrayList is a raw type. References to generic type
> ArrayList<E> should be parameterized" initially? I just did a fresh
> update (yes, I need to do it at home, too, so I can work on stuff) and
> these types of warnings are all over the place (at least in my Eclipse
> environment).
>
> Just curious what everyone things here ...
>
> Thanks,
>
> /dev/mrg
>>
--
Kevin Menard
Servprise International, Inc.
Remote reboot & power control for network equipment
www.servprise.com +1 508.892.3823 x308
Re: [JIRA] Closed: (CAY-904) Switch cayenne to Java 5: merge cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished
Posted by Michael Gentry <bl...@gmail.com>.
I apologize if this has been talked about before (I don't recall
seeing it), but are we going to worry about Java 5/Eclipse warnings
such as "ArrayList is a raw type. References to generic type
ArrayList<E> should be parameterized" initially? I just did a fresh
update (yes, I need to do it at home, too, so I can work on stuff) and
these types of warnings are all over the place (at least in my Eclipse
environment).
Just curious what everyone things here ...
Thanks,
/dev/mrg
On Nov 14, 2007 7:35 PM, Andrus Adamchik (JIRA) <de...@cayenne.apache.org> wrote:
>
> [ https://issues.apache.org/cayenne/browse/CAY-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Andrus Adamchik closed CAY-904.
> -------------------------------
>
> Resolution: Fixed
>
> Done. Things are looking good. Just get rid of 1.4 workspace in Eclipse. There are a few more things that may be cleaned up now, such as reflection based enum handlers , but we'll do it later
>
> > Switch cayenne to Java 5: merge cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished
> > ----------------------------------------------------------------------------------------
> >
> > Key: CAY-904
> > URL: https://issues.apache.org/cayenne/browse/CAY-904
> > Project: Cayenne
> > Issue Type: Task
> > Components: Cayenne Core Library
> > Affects Versions: 3.0
> > Reporter: Andrus Adamchik
> > Assignee: Andrus Adamchik
> > Fix For: 3.0
> >
> >
> > merge cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished , edit parent poms and assemblies.
> > Do not get rid of cayenne-jdk1.5-unpublished, as we may have to maintain the split JDK versions going forward when starting with 1.6 support
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[JIRA] Closed: (CAY-904) Switch cayenne to Java 5: merge
cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished
Posted by "Andrus Adamchik (JIRA)" <de...@cayenne.apache.org>.
[ https://issues.apache.org/cayenne/browse/CAY-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrus Adamchik closed CAY-904.
-------------------------------
Resolution: Fixed
Done. Things are looking good. Just get rid of 1.4 workspace in Eclipse. There are a few more things that may be cleaned up now, such as reflection based enum handlers , but we'll do it later
> Switch cayenne to Java 5: merge cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished
> ----------------------------------------------------------------------------------------
>
> Key: CAY-904
> URL: https://issues.apache.org/cayenne/browse/CAY-904
> Project: Cayenne
> Issue Type: Task
> Components: Cayenne Core Library
> Affects Versions: 3.0
> Reporter: Andrus Adamchik
> Assignee: Andrus Adamchik
> Fix For: 3.0
>
>
> merge cayenne-jdk1.4-unpublished to cayenne-jdk1.5-unpublished , edit parent poms and assemblies.
> Do not get rid of cayenne-jdk1.5-unpublished, as we may have to maintain the split JDK versions going forward when starting with 1.6 support
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.