Hi Pohl,

Yes, we are working on fixing issues raised in 1.6.2 release. You may
expect a 1.6.3 release mid of next week. Guess Sagara will be able to
add more on this.

Thanks
AmilaJ

On Thu, Jul 12, 2012 at 9:01 PM, Longsine, Pohl
<[email protected]> wrote:
> Thank you for referring me to that thread.  One question it does not
> answer is when 1.6.3 can be expected to be released.  Is it on a
> fast-track, given the unusual circumstance that 1.6.2 is now breaking
> builds out in the wild?
>
> On 7/11/12 9:59 PM, "Amila Jayasekara" <[email protected]> wrote:
>
>>Hi Pohl,
>>
>>You may find a similar discussion in [1]. This is mainly due to
>>Shibboleth has moved their repositories to some other location.
>>
>>Also we cannot do changes to released versions and we have fix this in
>>trunk and 1.6.3 branch.
>>
>>Thanks
>>AmilaJ
>>
>>[1]
>>http://mail-archives.apache.org/mod_mbox//axis-java-user/201207.mbox/%3CCA
>>[email protected]%3E
>>
>>On Thu, Jul 12, 2012 at 1:06 AM, Longsine, Pohl
>><[email protected]> wrote:
>>> Looks like the last time Jenkins built rampart (5 days, 21 hours ago) it
>>> included a change that was supposed to address this.
>>>
>>> Does this mean I need to wait for a 1.6.3 to be cut?
>>>
>>> https://builds.apache.org/job/Rampart/lastBuild/changes
>>> https://builds.apache.org/job/Rampart/
>>>
>>> From: <Longsine>, Gallup Gallup <[email protected]>
>>> Reply-To: "[email protected]" <[email protected]>
>>> Date: Wednesday, July 11, 2012 1:49 PM
>>> To: "[email protected]" <[email protected]>
>>> Subject: rampart 1.6.2 pom referencing broken Shibboleth repository
>>>
>>> Hello all, I am having a build problem with my projects, and I believe
>>>that
>>> I have traced the problem to the following in the rampart pom:
>>>
>>> <repositories>
>>> <repository>
>>> <releases>
>>> <enabled>true</enabled>
>>> <updatePolicy>always</updatePolicy>
>>> <checksumPolicy>warn</checksumPolicy>
>>> </releases>
>>> <snapshots>
>>> <enabled>true</enabled>
>>> <updatePolicy>never</updatePolicy>
>>> <checksumPolicy>warn</checksumPolicy>
>>> </snapshots>
>>> <id>open-saml</id>
>>> <name>OpenSAML</name>
>>> <url>http://shibboleth.internet2.edu/downloads/maven2/</url>
>>> </repository>
>>> </repositories>
>>>
>>>
>>> If you hit the above URL with your browser, you will see that this
>>> repository has been moved by their system administrator:
>>>
>>>>
>>>> The material has moved to a new home hosted by the Shibboleth
>>>>Consortium.
>>>> Click here to be redirected.
>>>>
>>>
>>> When maven attempts to download a jar from this repository, it
>>>apparently
>>> gets the 404 HTML page and writes it to disk in my ~/.m2/repositories
>>>cache
>>> using the *.jar file extension.
>>>
>>> Ultimately, this causes my build to fail when maven tries to unzip this
>>> "jar" and discovers that it doesn't conform to the zip file format
>>>(because,
>>> after all, no HTML does):
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>>> (default-compile) on project g-org: Compilation failure
>>> [ERROR] error: error reading
>>>
>>>/Users/pohl_longsine/.m2/repository/org/apache/xalan/xalan/2.7.1/xalan-2.
>>>7.1.jar;
>>> cannot read zip file
>>>
>>>
>>>
>>> orflongpmac:g pohl_longsine$ file
>>>
>>>/Users/pohl_longsine/.m2/repository/org/apache/xalan/xalan/2.7.1/xalan-2.
>>>7.1.jar
>>>
>>>/Users/pohl_longsine/.m2/repository/org/apache/xalan/xalan/2.7.1/xalan-2.
>>>7.1.jar:
>>> HTML document text
>>>
>>>
>>>
>>>
>>> orflongpmac:g pohl_longsine$ cat
>>>
>>>/Users/pohl_longsine/.m2/repository/org/apache/xalan/xalan/2.7.1/xalan-2.
>>>7.1.jar
>>> | grep moved
>>> <title>Internet2 Shibboleth Project has moved</title>
>>> <h3 align="center">The material has moved to a new home hosted by the
>>> Shibboleth Consortium. </h3>
>>>
>>>
>>> Am I correct in my assessment that your pom needs to be fixed?
>>>
>>>
>>>
>>>
>>> ________________________________
>>>
>>> IMPORTANT NOTICE: This e-mail message and all attachments, if any, may
>>> contain confidential and privileged material and are intended only for
>>>the
>>> person or entity to which the message is addressed. If you are not an
>>> intended recipient, you are hereby notified that any use, dissemination,
>>> distribution, disclosure, or copying of this information is
>>>unauthorized and
>>> strictly prohibited. If you have received this communication in error,
>>> please contact the sender immediately by reply e-mail, and destroy all
>>> copies of the original message.
>>>
>>> ________________________________
>>>
>>> IMPORTANT NOTICE: This e-mail message and all attachments, if any, may
>>> contain confidential and privileged material and are intended only for
>>>the
>>> person or entity to which the message is addressed. If you are not an
>>> intended recipient, you are hereby notified that any use, dissemination,
>>> distribution, disclosure, or copying of this information is
>>>unauthorized and
>>> strictly prohibited. If you have received this communication in error,
>>> please contact the sender immediately by reply e-mail, and destroy all
>>> copies of the original message.
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [email protected]
>>For additional commands, e-mail: [email protected]
>>
>
>
> ________________________________
>
> IMPORTANT NOTICE: This e-mail message and all attachments, if any, may 
> contain confidential and privileged material and are intended only for the 
> person or entity to which the message is addressed. If you are not an 
> intended recipient, you are hereby notified that any use, dissemination, 
> distribution, disclosure, or copying of this information is unauthorized and 
> strictly prohibited. If you have received this communication in error, please 
> contact the sender immediately by reply e-mail, and destroy all copies of the 
> original message.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to