upcoming cvs downtime notice
by Ruel Loehr
We are in the final stages of testing the CVS to svn migration. We are tentatively looking at a Thusday or Friday downtime of CVS which will affect all developers. A firm downtime notice will be sent tomorrow.
All existing users will have their permissions migrated. The only exception to this is non-employee committers who do not have an existing copywrite agreement on file.
The following link is a starting point for the contributor agreement:
http://labs.jboss.com/portal/con?noproject=true
Ruel Loehr
JBoss QA
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.4/396 - Release Date: 7/24/2006
19 years, 8 months
RE: [JBoss-dev] Invalid custom license
by Alejandro Guizar
Looks like Ruel noticed this problem and fixed it back in June. Thanks
Ruel!
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Alejandro Guizar
Developer, jBPM & Web Services
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> -----Original Message-----
> From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-
> bounces(a)lists.jboss.org] On Behalf Of Scott M Stark
> Sent: Tuesday, July 25, 2006 10:26 AM
> To: JBoss.org development list
> Subject: RE: [JBoss-dev] Invalid custom license
>
> There already was a jbpm-bpel.txt in licenses and the current bpel
> component info was referring to it. My local copy was out of date.
>
> > -----Original Message-----
> > From: jboss-development-bounces(a)lists.jboss.org
> > [mailto:jboss-development-bounces@lists.jboss.org] On Behalf
> > Of Scott M Stark
> > Sent: Tuesday, July 25, 2006 8:13 AM
> > To: JBoss.org development list
> > Subject: [JBoss-dev] Invalid custom license
> >
> > jboss-head will not build for me due to this invalid custom
> > license reference by jbpm-bpel:
> >
> > <project name="jbpm-component-info">
> >
> > <component id="jbpm-bpel"
> > licenseType="custom"
> > version="1.0.0.alpha4"
> > projectHome="http://jbpm.org/"
> > description="Powerful orchestration platform">
> >
> > <artifact id="jbpm-bpel.jar"/>
> >
> > <import componentref="jbpm">
> > <compatible version="3.0.2"/>
> > </import>
> >
> > <export>
> > <include input="jbpm-bpel.jar"/>
> > </export>
> >
> > </component>
> >
> > </project>
> >
> > You cannot add libraries to the repository that do not have a
> > corresponding txt file in the
> > http://repository.jboss.com/licenses/ directory. This license
> > type should also be named bpel-lgpl or the like as well.
> >
> > xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Scott Stark
> > VP Architecture & Technology
> > JBoss, a division of Red Hat
> > xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >
> >
> > _______________________________________________
> > 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
19 years, 8 months
RE: [JBoss-dev] Invalid custom license
by Scott M Stark
There already was a jbpm-bpel.txt in licenses and the current bpel
component info was referring to it. My local copy was out of date.
> -----Original Message-----
> From: jboss-development-bounces(a)lists.jboss.org
> [mailto:jboss-development-bounces@lists.jboss.org] On Behalf
> Of Scott M Stark
> Sent: Tuesday, July 25, 2006 8:13 AM
> To: JBoss.org development list
> Subject: [JBoss-dev] Invalid custom license
>
> jboss-head will not build for me due to this invalid custom
> license reference by jbpm-bpel:
>
> <project name="jbpm-component-info">
>
> <component id="jbpm-bpel"
> licenseType="custom"
> version="1.0.0.alpha4"
> projectHome="http://jbpm.org/"
> description="Powerful orchestration platform">
>
> <artifact id="jbpm-bpel.jar"/>
>
> <import componentref="jbpm">
> <compatible version="3.0.2"/>
> </import>
>
> <export>
> <include input="jbpm-bpel.jar"/>
> </export>
>
> </component>
>
> </project>
>
> You cannot add libraries to the repository that do not have a
> corresponding txt file in the
> http://repository.jboss.com/licenses/ directory. This license
> type should also be named bpel-lgpl or the like as well.
>
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Scott Stark
> VP Architecture & Technology
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>
19 years, 8 months
Log4j ugrade?
by Dimitris Andreadis
Should we consider upgrading log4j? Any obvious reasons not to upgrade?
We are at <componentref name="apache-log4j" version="1.2.8"/>
And the latest is:
log4j version 1.2.13
Log4j version 1.2.13 contains several bug fixes related to the TRACE
level introduced in version 1.2.12 and a fix in the ConsoleAppender for
a bug that affected JBoss.
The next major release of log4j will be version 1.3. It will contain
many new features and changes, and if you have written custom code, it
may need to be modified to work with it. Please see the document
entitled preparing for log4j 1.3 for a more detailed discussion.
See also
http://jira.jboss.com/jira/browse/JBAS-3316
19 years, 8 months
Invalid custom license
by Scott M Stark
jboss-head will not build for me due to this invalid custom license
reference by jbpm-bpel:
<project name="jbpm-component-info">
<component id="jbpm-bpel"
licenseType="custom"
version="1.0.0.alpha4"
projectHome="http://jbpm.org/"
description="Powerful orchestration platform">
<artifact id="jbpm-bpel.jar"/>
<import componentref="jbpm">
<compatible version="3.0.2"/>
</import>
<export>
<include input="jbpm-bpel.jar"/>
</export>
</component>
</project>
You cannot add libraries to the repository that do not have a
corresponding txt file in the
http://repository.jboss.com/licenses/ directory. This license type
should also be named bpel-lgpl or the like as well.
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
VP Architecture & Technology
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
19 years, 8 months
