Re: [jira] Assigned: (GERONIMO-4017) pluto need to be update

[Donald Woods]

They are not published, but in our private repository directory. I didn't see where changing the pinned version number would be worth the effort of updating the pom.xml and generating a new set of repository directories. Also, the version number is based on the Pluto revision level, which had not changed....

-Donald


David Jencks wrote:

On May 19, 2008, at 8:39 PM, Donald Woods wrote:

No, the latest jars fixed the Console failures in the 2.1 branch.

Everything passed on trunk in the 5/18 4:33PM build notification, so any errors you are seeing now are probably related to other changes or to timing/load issues on Jarek's machine....

thanks
david jencks

I talked with jarek on irc and he suggested that I kill my local m2 repo pluto artifacts, and doing so made these tests pass. However.... I think this means that we have 2 non-snapshot jars out with the same name and different contents, which is a giant no-no. Is this true? How did it happen? Can we change the name of at least one of the jars?

-Donald


David Jencks wrote:

AFAICT this is still broken?

thanks
david jencks
On May 14, 2008, at 8:47 AM, Donald Woods (JIRA) wrote:

I think this is causing errors in the testsuite/consoletestsuite advanced for the jms server test and possibly others.

[ https://issues.apache.org/jira/browse/GERONIMO-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Donald Woods reassigned GERONIMO-4017:
--------------------------------------

  Assignee: Donald Woods

pluto need to be update
-----------------------

              Key: GERONIMO-4017
              URL: https://issues.apache.org/jira/browse/GERONIMO-4017
          Project: Geronimo
       Issue Type: Bug
   Security Level: public(Regular issues)
       Components: console
 Affects Versions: 2.1.2, 2.1.x
         Reporter: YunFeng Ma
         Assignee: Donald Woods
         Priority: Critical
          Fix For: 2.1.2, 2.1.x



The one we used now:

Some functionalities (such as add Tomcat BIO HTTP Connector) of admin console fails because pluto can not handle the question mark in the url. The pluto trunk fixed this. https://svn.apache.org/repos/asf/portals/pluto/branches/pluto-1.1.x/pluto-portal-driver-impl/src/main/java/org/apache/pluto/driver/url/impl/PortalURLParserImpl.java

The trunk version:

https://svn.apache.org/repos/asf/portals/pluto/trunk/pluto-portal-driver-impl/src/main/java/org/apache/pluto/driver/url/impl/PortalURLParserImpl.java

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

smime.p7s
Description: S/MIME Cryptographic Signature