Maven Upload Requests

Upload request for swingx 0.9 for jdk 1.5

Details

  • Type: Task Task
  • Status: Closed Closed
  • Resolution: Fixed
  • Labels:
    None

Description

SwingX is all about Swing components. It focuses both on extensions to existing Swing components as well as brand new ones. SwingX contains a lot of great components that you can use in your applications today.

Issue Links

This issue is duplicated by:
MAVENUPLOAD-1800 Upload request for swingx 0.9 for jdk 1.6 Closed
This issue is related to:
MAVENUPLOAD-1800 Upload request for swingx 0.9 for jdk 1.6 Closed
This issue depends upon:
MAVENUPLOAD-1802 Upload request for swinglayout Closed
MAVENUPLOAD-1803 Upload request for swingworker Closed
MAVENUPLOAD-1801 Upload request for multiplegradientpaint Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Carlos Sanchez added a comment -
next time please put all urls in only one jira

classifiers are used when the same code produce two different jars. The pom and sources must be the same.
And there s no filed classifier in the pom, so yours doesnt validate
Show
Carlos Sanchez added a comment - next time please put all urls in only one jira classifiers are used when the same code produce two different jars. The pom and sources must be the same. And there s no filed classifier in the pom, so yours doesnt validate
Hide
Permalink
Wim Deblauwe added a comment -
How do you propose I change them? The people from swingx say that the same jar can be used with jdk 1.5 and jdk 1.6, only for jdk 1.6 you don't need some of the dependencies (since they are already part of the jdk). That is why I thought of using classifiers (like TestNG does).

I would like to avoid that people need to start excluding dependencies if they use jdk 1.6.

Any help on this would be highly appreciated.
Show
Wim Deblauwe added a comment - How do you propose I change them? The people from swingx say that the same jar can be used with jdk 1.5 and jdk 1.6, only for jdk 1.6 you don't need some of the dependencies (since they are already part of the jdk). That is why I thought of using classifiers (like TestNG does). I would like to avoid that people need to start excluding dependencies if they use jdk 1.6. Any help on this would be highly appreciated.
Hide
Permalink
Jan Haderka added a comment -
Indeed. All the dependencies are core components in JDK 1.6.
This is the nature of swinglabs projects - prepare things to be put on jdk in future versions.
Therefore swing-layout, swing-worker and multiple-gradient-paints need to be included for jdk 1.5, but since they made it into JDK 1.6 they are not needed there.

Jar file is same in both cases since we resolve dependencies dynamically at runtime to make sure that running one application at different JDKs is as easy and simple as possible.

As a side note: I will release SwingX 0.9.1 in next few days, so if we can just figure out what the bundle should look like and then we create and upload 0.9.1 directly.
Show
Jan Haderka added a comment - Indeed. All the dependencies are core components in JDK 1.6. This is the nature of swinglabs projects - prepare things to be put on jdk in future versions. Therefore swing-layout, swing-worker and multiple-gradient-paints need to be included for jdk 1.5, but since they made it into JDK 1.6 they are not needed there. Jar file is same in both cases since we resolve dependencies dynamically at runtime to make sure that running one application at different JDKs is as easy and simple as possible. As a side note: I will release SwingX 0.9.1 in next few days, so if we can just figure out what the bundle should look like and then we create and upload 0.9.1 directly.
Hide
Permalink
Carlos Sanchez added a comment -
if the jar is the same you don't need classifiers, just one jar and one pom with profiles inside with the different dependencies that get activated based on the jdk version

http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Show
Carlos Sanchez added a comment - if the jar is the same you don't need classifiers, just one jar and one pom with profiles inside with the different dependencies that get activated based on the jdk version http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Hide
Permalink
Wim Deblauwe added a comment -
Thanks for that, did not know it could be done like that. I will check it out more thouroughly and comment if I got an update of the bundle.
Show
Wim Deblauwe added a comment - Thanks for that, did not know it could be done like that. I will check it out more thouroughly and comment if I got an update of the bundle.
Hide
Permalink
Wim Deblauwe added a comment -
Hi,

can you take a look at the attached pom.xml and let me know if it is ok like that? The idea is to only have the 3 dependencies in the profile activated when jdk 1.5 is running and not jdk 1.6

regards,

Wim
Show
Wim Deblauwe added a comment - Hi, can you take a look at the attached pom.xml and let me know if it is ok like that? The idea is to only have the 3 dependencies in the profile activated when jdk 1.5 is running and not jdk 1.6 regards, Wim
Hide
Permalink
Carlos Sanchez added a comment -
looks good to me, have you tried it with your projects ?
Show
Carlos Sanchez added a comment - looks good to me, have you tried it with your projects ?
Hide
Permalink
Wim Deblauwe added a comment -
Just tested it now and seems to work great. I mailed the bundle jar to Jan and he will let know where and when it is available.
Show
Wim Deblauwe added a comment - Just tested it now and seems to work great. I mailed the bundle jar to Jan and he will let know where and when it is available.
Hide
Permalink
Wim Deblauwe added a comment -
Thank you Carlos!
Show
Wim Deblauwe added a comment - Thank you Carlos!

People

Vote (3)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.