List Info

Thread: Re:




Re:
user name
2008-04-21 03:39:53
Guys, the team has been locked in a room in the last two
weeks, 
componentizing the build. Dimitris is in close touch with
the very few 
persons that still need to deliver the SPI/releases. Once
this is done, 
we should clearly be able to see much more stability.
Dimitris will send 
new "guidelines" to this ML once all releases/SPI
will have been 
contributed. Stay tuned.

Cheers,


sacha


On 04/18/2008 07:24 PM, Andrew Lee Rubinger wrote:
> Clebert Suconic wrote:
>> Ok... these are the current snapshots we have...
maybe we should start 
>> getting rid of them (next update to any of these
snapshots should 
>> include any sort of UniqueIDs)
> 
> Thank you for this audit, Clebert.
> 
> I'm sure Dimitris and the rest of the AS team would
appreciate any help 
> that could be given towards the definition of SPIs
where some are 
> lacking, resolving cyclic dependencies, and making
releases of the 
> current snapshots.  He's the point guy for any
questions on this front.
> 
> Brian is already working on Clustering, Anil on
Security.  The aspects 
> mentioned are now in
repos/jbossas/projects/jboss-aspects and (I 
> believe) are nearly ready for release, pending some
more love to 'em.
> 
>> EJB3 has a bunch (but there is a version number on
each one.. maybe 
>> this is okay)
> 
> Nope, EJB3 team is looking forward to a proper release
next week, but 
> until our transitive dependencies all have releases, we
can't deliver 
> that yet. 
> 
> Been pushing hard the past couple weeks towards that
end. ;)
> 
> 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

AS5 targets/guidelines (was: maven gripes)
user name
2008-04-21 04:47:58
Sacha Labourey wrote:
> Guys, the team has been locked in a room in the last
two weeks, 
> componentizing the build. Dimitris is in close touch
with the very few 
> persons that still need to deliver the SPI/releases.
Once this is done, 
> we should clearly be able to see much more stability.
Dimitris will send 
> new "guidelines" to this ML once all
releases/SPI will have been 
> contributed. Stay tuned.
> 
> Cheers,
> 
> sacha

The current set of targets/guidelines include:

============

- Complete the componetization of EJB3 (so it can be
released) by breaking out remaining 
cyclical dependencies: In the current component dependency
list we have:

- Security aspect & AS security module, Anil
- AS connector module/spi, Jasper
- Clustering aspects, Brian
- EJB3/WS spi, Heiko
- EJB3 core depending on jbossAS classes, Carlo

Those aspects were already broken out:
- asynch
- currentinvocation
- remoting
- transaction

===============

- No further changes to the AS build. The thirdparty
directory is now backed by the maven 
repo and that seems to work well (minus the gripes). In
order not to disrupt the builds we 
will leave the full mavenization of the AS build for later.

===============

- No more SNAPSHOTs (or re-tagging of releases). Please use
tagged releases for whatever 
goes in the AS build. The current snapshots that come
directly or indirectly to AS that we 
need to get rid of are:

(cd thirdparty; mvn -U dependency:tree | grep SNAPSHOT)
[INFO]
org.jboss.jbossas:jboss-as-thirdparty:pom:5.0.0-SNAPSHOT
[INFO] +-
org.jboss.javaee:jboss-servlet-api:jar:2.5.0-SNAPSHOT:compil
e
[INFO] +-
org.jboss.aspects:jboss-security-aspects:jar:1.0.0-SNAPSHOT:
compile
[INFO] +-
org.jboss.deployers:jboss-deployers-vfs:jar:2.0.0-SNAPSHOT:c
ompile
[INFO] |  -
org.jboss.deployers:jboss-deployers-core:jar:2.0.0-SNAPSHOT:
compile

[INFO] +- org.jboss:jboss-vfs:jar:2.0.0-SNAPSHOT:compile
[INFO] +-
org.jboss.ejb3:jboss-ejb3-core:jar:jboss-ejb3-client:0.1.0-S
NAPSHOT:co
mpile
[INFO] |  +-
org.jboss.ejb3:jboss-ejb3-interceptors:jar:0.13.0-SNAPSHOT:c
ompile
[INFO] +-
org.jboss.javaee:jboss-jms-api:jar:1.1.0-SNAPSHOT:compile
[INFO] +-
org.jboss.deployers:jboss-deployers-client-spi:jar:2.0.0-SNA
PSHOT:comp
ile
[INFO] +-
org.jboss.javaee:jboss-jca-api:jar:1.5.0-SNAPSHOT:compile
[INFO] +-
org.jboss.javaee:jboss-ejb-api:jar:3.0.0-SNAPSHOT:compile
[INFO] +-
org.jboss.cluster:jboss-ha-client:jar:1.1.0-SNAPSHOT:compile

[INFO] |  -
org.jboss.aspects:jboss-remoting-aspects:jar:1.0.0-SNAPSHOT:
compile

[INFO] +-
org.jboss.javaee:jboss-javaee:jar:5.0.0-SNAPSHOT:compile
[INFO] +-
org.jboss.javaee:jboss-jacc-api:jar:1.1.0-SNAPSHOT:compile
[INFO] +-
org.jboss.deployers:jboss-deployers-impl:jar:2.0.0-SNAPSHOT:
compile
[INFO] +-
org.jboss.deployers:jboss-deployers-spi:jar:2.0.0-SNAPSHOT:c
ompile
[INFO] +-
org.jboss.deployers:jboss-deployers-vfs-spi:jar:2.0.0-SNAPSH
OT:compile

[INFO] +-
org.jboss.ejb3:jboss-ejb3-core:jar:0.1.0-SNAPSHOT:compile
[INFO] +-
org.jboss.ejb3:jboss-ejb3-cache:jar:0.13.0-SNAPSHOT:compile
[INFO] +-
jboss.jbossws-framework:jbossws-framework:jar:3.0.2-SNAPSHOT
:compile
[INFO] +-
org.jboss.deployers:jboss-deployers-core-spi:jar:2.0.0-SNAPS
HOT:compil
e
[INFO] +-
org.jboss.deployers:jboss-deployers-client:jar:2.0.0-SNAPSHO
T:compile
[INFO] +-
org.jboss.deployers:jboss-deployers-structure-spi:jar:2.0.0-
SNAPSHOT:c
ompile
[INFO] +-
jboss.jbossws-framework:resources:jar:3.0.2-SNAPSHOT:compile

[INFO] +-
org.jboss.ejb3:jboss-ejb3-security:jar:0.13.0-SNAPSHOT:compi
le
[INFO] +-
org.jboss.javaee:jboss-persistence-api:jar:3.0.0-SNAPSHOT:co
mpile
[INFO] +-
jboss.jbossws-common:jbossws-common:jar:1.0.5-SNAPSHOT:compi
le
[INFO] +-
org.jboss.javaee:jboss-jaspi-api:jar:1.0.0-SNAPSHOT:compile
[INFO] +-
org.jboss.cluster:jboss-ha-server-api:jar:1.1.0-SNAPSHOT:com
pile
[INFO] +-
org.jboss.javaee:jboss-jad-api:jar:1.2.0-SNAPSHOT:compile
[INFO] -
org.jboss.aspects:jboss-transaction-aspects:jar:1.0.0-SNAPSH
OT:compile

=====================

- Complete component updates. Expecting deliverables from:

hibernate
jboss/pojo-cache
security
vfs
remoting
integration
metadata
microcontainer

full list: http://ji
ra.jboss.com/jira/browse/JBAS-5121

=====================

- JDK5 will be the basis of all our TCK testing. All code
should be compiled with JDK5 and 
be able to run with both JDK5/6. We need to adapt our
testsuite to test for the later scenario.

=====================

- The number of JBAS JIRA are going up instead of going
down. Please take a look at what has 
been assign to you or created by you and change the priority
to Critical/Blocker, if it must 
make it for AS5 CR1, or reschedule it.

JBossAS 5.0.0.CR1 tasks assigned to me
http://jira.jboss.com/jira
/secure/IssueNavigator.jspa?mode=hide&requestId=12311444


JBossAS 5.0.0.CR1 tasks reported by me
http://jira.jboss.com/jira
/secure/IssueNavigator.jspa?mode=hide&requestId=12311445


I'm going to reschedule all non Blocker/Critical issues very
soon.

=====================

- Testsuite, thanks to Brian, Adrian, Shelly and others we
are under ~200 failures! My 
proposal would be to exclude tests that don't make much
sense and nobody has cared to look 
at for the past year or so.

http://hudson.qa.jboss.
com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun1
5/532/

====================

Once things are stabilized we'll try to come up with a new
estimate for the AS5 CR1 delivery 
date.

Thanks
/Dimitris
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )