You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@abdera.apache.org by "Glen Daniels (JIRA)" <ji...@apache.org> on 2008/02/17 03:13:09 UTC

[jira] Created: (ABDERA-122) Client module using older version of Jetty - confuses IDEA

Client module using older version of Jetty - confuses IDEA
----------------------------------------------------------

                 Key: ABDERA-122
                 URL: https://issues.apache.org/jira/browse/ABDERA-122
             Project: Abdera
          Issue Type: Bug
            Reporter: Glen Daniels
         Attachments: jetty-version.patch

Hey folks.  The abdera-client module was set to use jetty v6.0.0rc0, whereas every other module seems to be using the current 6.1.5 version.  This caused me some grief debugging in IDEA, which disappeared once I corrected the version.

My solution for this is attached in a patch - basically I just replaced ALL the jetty versions in various poms with ${jetty.version}, and then defined that property in the parent pom.  I'd like to suggest that Abdera consider this pattern in a broader sense - we've used it to good effect in the WS projects, and it makes it much easier to keep things in sync.

Much appreciated if someone could commit this for me.  Thanks!


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (ABDERA-122) Client module using older version of Jetty - confuses IDEA

Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ABDERA-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Glen Daniels updated ABDERA-122:
--------------------------------

    Attachment: jetty-version.patch

POM patch to rationalize jetty version across the project

> Client module using older version of Jetty - confuses IDEA
> ----------------------------------------------------------
>
>                 Key: ABDERA-122
>                 URL: https://issues.apache.org/jira/browse/ABDERA-122
>             Project: Abdera
>          Issue Type: Bug
>            Reporter: Glen Daniels
>         Attachments: jetty-version.patch
>
>
> Hey folks.  The abdera-client module was set to use jetty v6.0.0rc0, whereas every other module seems to be using the current 6.1.5 version.  This caused me some grief debugging in IDEA, which disappeared once I corrected the version.
> My solution for this is attached in a patch - basically I just replaced ALL the jetty versions in various poms with ${jetty.version}, and then defined that property in the parent pom.  I'd like to suggest that Abdera consider this pattern in a broader sense - we've used it to good effect in the WS projects, and it makes it much easier to keep things in sync.
> Much appreciated if someone could commit this for me.  Thanks!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (ABDERA-122) Client module using older version of Jetty - confuses IDEA

Posted by "James M Snell (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ABDERA-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James M Snell resolved ABDERA-122.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.4.0

checked in

> Client module using older version of Jetty - confuses IDEA
> ----------------------------------------------------------
>
>                 Key: ABDERA-122
>                 URL: https://issues.apache.org/jira/browse/ABDERA-122
>             Project: Abdera
>          Issue Type: Bug
>            Reporter: Glen Daniels
>             Fix For: 0.4.0
>
>         Attachments: jetty-version.patch
>
>
> Hey folks.  The abdera-client module was set to use jetty v6.0.0rc0, whereas every other module seems to be using the current 6.1.5 version.  This caused me some grief debugging in IDEA, which disappeared once I corrected the version.
> My solution for this is attached in a patch - basically I just replaced ALL the jetty versions in various poms with ${jetty.version}, and then defined that property in the parent pom.  I'd like to suggest that Abdera consider this pattern in a broader sense - we've used it to good effect in the WS projects, and it makes it much easier to keep things in sync.
> Much appreciated if someone could commit this for me.  Thanks!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.