AOP 2.0.0.alpha1, 2.0.0.beta1 and 2.0.0.beta2 depend on this.
I think it was Paul's idea to put it under org/jboss. I have reinstated
org/jboss/jboss-retro/1.1.2 in the repository, so my old builds still
work and updated aop trunk to reference jboss/jboss-retro/1.1.2
Dimitris Andreadis wrote:
This is the move, but as Scott said org/jboss was not used in the old
repository, so maybe we should just do a copy. What depends on the old
location?
---
Author: thomas.diesler(a)jboss.com
Date: 2007-11-01 04:02:14 -0400 (Thu, 01 Nov 2007)
New Revision: 1739
Added:
jboss/jboss-retro/
Removed:
org/jboss/jboss-retro/
Log:
Move jboss-retro
Copied: jboss/jboss-retro (from rev 1738, org/jboss/jboss-retro)
Scott M Stark wrote:
> I don't know why anything would be under org/jboss in the legacy
> repository. I don't see anything there. Such content should be under the
> maven2 repo (
http://repository.jboss.org/maven2), and I do see this
> version there:
>
>
http://repository.jboss.org/maven2/org/jboss/jboss-retro/
>
>
> Kabir Khan wrote:
>> It used to be here:
>>
http://repository.jboss.org/org/jboss/jboss-retro/1.1.2/component-info.xml
>>
>> It has suddenly been removed so the aop build fails.
>>
>> AOP 2.0.0.beta2 (and maybe older versions, haven't checked) used this
>> version so how can we have reproducible builds if things like this keep
>> disappearing/being moved?
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Kabir Khan
JBoss AOP Lead
JBoss, a division of Red Hat