Java 7

[Jeff Ramsdale]

Just tried to compile the latest Rio and received an error:

[INFO] ------------------------------------------------------------------------

[INFO] Building Module :: Rio Management User Interface 5.0-M2

[INFO] ------------------------------------------------------------------------

[INFO] 

[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ rio-ui ---

[INFO] Deleting /Users/jramsdale/workspaces/rio/rio-project/rio-tools/rio-ui/target

[INFO] 

[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ rio-ui ---

[debug] execute contextualize

[INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] Copying 18 resources

[INFO] 

[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ rio-ui ---

[INFO] Compiling 71 source files to /Users/jramsdale/workspaces/rio/rio-project/rio-tools/rio-ui/target/classes

[INFO] -------------------------------------------------------------

[ERROR] COMPILATION ERROR : 

[INFO] -------------------------------------------------------------

[ERROR] /Users/jramsdale/workspaces/rio/rio-project/rio-tools/rio-ui/src/main/java/org/rioproject/tools/ui/servicenotification/filter/FilterPanel.java:[42,27] type javax.swing.JComboBox does not take parameters

[ERROR] /Users/jramsdale/workspaces/rio/rio-project/rio-tools/rio-ui/src/main/java/org/rioproject/tools/ui/servicenotification/filter/FilterPanel.java:[56,35] type javax.swing.JComboBox does not take parameters

[INFO] 2 errors 

Looks like Java 7 is required to compile Rio?

-jeff

[Dennis Reedy]

Hi Jeff,

Yes, Java 7 is required. Is that an issue? Java 6 EOL is this month, do you need Java 6 with Rio in your environment? 

Dennis

--
You received this message because you are subscribed to the Google Groups "Rio Developers Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rio-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Jeff Ramsdale]

I'm still just doing Rio on my own but would like to see some experimenting at the office. It looks like we haven't yet made the jump to Java 7, but that's probably inertia more than anything. For my own part I've been avoiding it due to Sun's failure to provide a test kit and all the politics around that (though admittedly I haven't tracked the issue closely). That's a doomed battle at this point, though, and I'll probably update when the team does.

In any case I'm not sure if the docs or poms declare the requirement so if it's truly required it should probably be captured somewhere.

-j

[Dennis Reedy]

I think the issue is using generics for a JComboBox, I think I can back that one out without too much of an issue :) Also, although I've released 5.0-M2 I am planning a small update to that (too include this issue) that will overwrite the current M2 release. I know this kind of breaks the rules, but its a small update.

Thanks

Dennis

[Jeff Ramsdale]

Well, not only does it break the rules it might not be effective. Anyone who has built or depends on that release will not get the updated one. Maven only replaces snapshot releases when resolving artifacts.

-j

[Dennis Reedy]

On Feb 8, 2013, at 744PM, Jeff Ramsdale wrote:

> Well, not only does it break the rules it might not be effective. Anyone who has built or depends on that release will not get the updated one. Maven only replaces snapshot releases when resolving artifacts.

Yes, I realize that. The client that is the major contributor to the ongoing development of Rio has requested that I do exactly this.

Regards

Dennis

[Jeff Ramsdale]

Ah, sadness. I understand reality, though. If you could, let us know on the list any time this happens (as you are now) so we can blow away our local Rio artifacts to make sure they are re-resolved. Or, is this to pick up the new (not yet available) River artifacts? I guess either way we'll need to know what artifacts need to be replaced...

-j

[Dennis Reedy]

On Feb 8, 2013, at 816PM, Jeff Ramsdale wrote:

Ah, sadness. I understand reality, though. If you could, let us know on the list any time this happens (as you are now) so we can blow away our local Rio artifacts to make sure they are re-resolved. Or, is this to pick up the new (not yet available) River artifacts? I guess either way we'll need to know what artifacts need to be replaced...

Of course, and indeed I will if anything changes for Rio and what I release. Also, things may change, and M3 could happen earlier then planned (especially with the new River artifacts). BTW, if you (or anyone) have anything that you want to add to the 5.0 pipeline, or feedback on what is in the pipeline, contribute to https://github.com/dreedyman/Rio/issues

Thanks

Dennis