jbossas/projects/jboss-aspects/trunk/security Broken

Not sure who the owner is here (Dimitris, Anil?), but
compilation fails 
on this component.

Hoping for a release here soon; it's a dependency for an
EJB3 Core CR1. 

S,
ALR
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

Tell me what happens when you do a svn delete on that. If it
works in 
your workspace, fine by me.

Andrew Lee Rubinger wrote:
> Not sure who the owner is here (Dimitris, Anil?), but
compilation fails 
> on this component.
> 
> Hoping for a release here soon; it's a dependency for
an EJB3 Core CR1. 
> 
> S,
> ALR
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

For the record, ASPECT-6 dealt with this and resolved by
ALR.

Anil Saldhana wrote:
> Tell me what happens when you do a svn delete on that.
If it works in 
> your workspace, fine by me.
> 
> Andrew Lee Rubinger wrote:
>> Not sure who the owner is here (Dimitris, Anil?),
but compilation 
>> fails on this component.
>>
>> Hoping for a release here soon; it's a dependency
for an EJB3 Core 
>> CR1. 
>>
>> S,
>> ALR
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

I hope nobody is using the aspects you've just deleted. They
were packaged in 
jboss-aspect-jdk50-client.jar &
jboss-aspect-deployer-jdk50.jar.

For now it will work because it uses the
org.jboss.aspects:jboss-security-aspects snapshot 
which is still there.

jboss-head/aspects/build.xml:
...
       <!-- Build client jar containing the minimum
needed for ejb 3 -->
       <jar
destfile="${build.lib}/jboss-aspect-jdk50-client.jar&qu
ot;
...
          <!-- include the broken out security aspects in
the client lib -->
          <zipfileset
src="${org.jboss.aspects.lib}/jboss-security-aspects.ja
r">
             <include
name="org/jboss/aspects/security/SecurityClientIntercep
tor.class"/>
             <include
name="org/jboss/aspects/security/SecurityActions*.class
"/>
          </zipfileset>
...
       <!-- Build jboss-aspect-deployer-jdk50.jar -->
       <jar
destfile="${build.lib}/jboss-aspect-library-jdk50.jar&q
uot;
...
         <!-- include the broken out security aspects in
the lib -->
         <zipfileset
src="${org.jboss.aspects.lib}/jboss-security-aspects.ja
r">
             <include
name="org/jboss/aspects/security/**.class"/>
          </zipfileset>

Anil Saldhana wrote:
> For the record, ASPECT-6 dealt with this and resolved
by ALR.
> 
> Anil Saldhana wrote:
>> Tell me what happens when you do a svn delete on
that. If it works in 
>> your workspace, fine by me.
>>
>> Andrew Lee Rubinger wrote:
>>> Not sure who the owner is here (Dimitris,
Anil?), but compilation 
>>> fails on this component.
>>>
>>> Hoping for a release here soon; it's a
dependency for an EJB3 Core 
>>> CR1. 
>>>
>>> S,
>>> ALR
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

I'm iffy about this deletion, too.  I've got *no idea* what
depends on 
this aspect.

I can go into the Maven2 Snapshots Repo via DAV and remove
the Aspect 
from there, and see what fails, or we can put it back and
have someone 
fix it so it doesn't break the build.

How would you like to handle this one, Dimitris?

S,
ALR

Dimitris Andreadis wrote:
> I hope nobody is using the aspects you've just deleted.
They were 
> packaged in jboss-aspect-jdk50-client.jar & 
> jboss-aspect-deployer-jdk50.jar.
> 
> For now it will work because it uses the 
> org.jboss.aspects:jboss-security-aspects snapshot which
is still there.
> 
> jboss-head/aspects/build.xml:
> ...
>       <!-- Build client jar containing the minimum
needed for ejb 3 -->
>       <jar
destfile="${build.lib}/jboss-aspect-jdk50-client.jar&qu
ot;
> ...
>          <!-- include the broken out security
aspects in the client lib -->
>          <zipfileset 
>
src="${org.jboss.aspects.lib}/jboss-security-aspects.ja
r">
>             <include 
>
name="org/jboss/aspects/security/SecurityClientIntercep
tor.class"/>
>             <include 
>
name="org/jboss/aspects/security/SecurityActions*.class
"/>
>          </zipfileset>
> ...
>       <!-- Build jboss-aspect-deployer-jdk50.jar
-->
>       <jar
destfile="${build.lib}/jboss-aspect-library-jdk50.jar&q
uot;
> ...
>         <!-- include the broken out security aspects
in the lib -->
>         <zipfileset 
>
src="${org.jboss.aspects.lib}/jboss-security-aspects.ja
r">
>             <include
name="org/jboss/aspects/security/**.class"/>
>          </zipfileset>
> 
> Anil Saldhana wrote:
>> For the record, ASPECT-6 dealt with this and
resolved by ALR.
>>
>> Anil Saldhana wrote:
>>> Tell me what happens when you do a svn delete
on that. If it works in 
>>> your workspace, fine by me.
>>>
>>> Andrew Lee Rubinger wrote:
>>>> Not sure who the owner is here (Dimitris,
Anil?), but compilation 
>>>> fails on this component.
>>>>
>>>> Hoping for a release here soon; it's a
dependency for an EJB3 Core 
>>>> CR1. 
>>>>
>>>> S,
>>>> ALR
> _______________________________________________
> jboss-development mailing list
> jboss-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment