September 2006 - jboss-development

jboss-4.0-testsuite-1.6 Build Failed

by qa＠jboss.com

19 years, 10 months

1
0
0 / 0

jboss-4.0-testsuite-1.5 Build Completed With Testsuite Errors

by qa＠jboss.com

19 years, 10 months

1
0
0 / 0

RE: [JBoss-dev] common project structure changes

by Ruel Loehr

Done. You just have to tell the jar plugin the name you wish you use if you don't want to accept the default.  <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> <executions> <execution> <goals> <goal>jar</goal> </goals> </execution> </executions> <configuration> <jarName>jboss-xml-binding</jarName> </configuration> </plugin> Ruel Loehr JBoss, a division of Red Hat QA ----------------------------- 512-342-7840 ext 2011 Yahoo: ruelloehr Skype: ruelloehr AOL: dokoruel -----Original Message----- From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Alexey Loubyansky Sent: Friday, September 01, 2006 8:56 AM To: JBoss.org development list Subject: Re: [JBoss-dev] common project structure changes Ruel, could you take care if this? I'd do it myself, but not sure how. The default format is artifactId + '-' + version. And the version is required. Is there a way to change the format. A workaround would be <artifactId>jboss-xml</artifactId> <version>binding</version> :) Thanks! Alexey Scott M Stark wrote: > It should still be called jboss-xml-binding.jar > > Alexey Loubyansky wrote: >> jbossxb output changed from jboss-xml-binding.jar to jbossxb.jar. If >> it's going to be called this way now we'll have to update references >> to it in the repository. >> > > _______________________________________________ > 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 -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.7/435 - Release Date: 8/31/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.7/435 - Release Date: 8/31/2006

19 years, 10 months

1
0
0 / 0

JBoss AOP 1.5.1 released

by Kabir Khan

The main focus the past few months has been on the upcoming 2.0 version and integration of that with the microcontainer. This 1.5.1.GA release contains bugfixes from the JBoss 1.5.0 release, and is the version of aop that will be bundled with JBoss AS 4.0.5.CR1 The release notes for 1.5.1 can be found here: http://jira.jboss.com/jira/secure/ReleaseNote.jspa?version=12310806&styleNam e=Html&projectId=10055 And it can be downloaded from here: http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=84165 &release_id=443930 Enjoy, and keep the feedback coming through the user forum: http://www.jboss.com/index.html?module=bb&op=viewforum&f=236 Kabir

19 years, 10 months

1
0
0 / 0

common project structure changes

by Ruel Loehr

We’ve been working on the file structure of the jboss common project and are now ready to merge the changes back into the trunk. The changes are substantial, so I want to make sure everyone is clear before I commit them in. Currently the common project consists of 1 source tree which creates 4 artifacts: Jboss-archive-browsing.jar Jboss-common.jar Jboss-common-client.jar Namespace.jar The project has been refactored in a branch (HYPERLINK "https://svn.jboss.org/repos/common/branches/logging_refactoring/"https://svn.jboss.org/repos/common/branches/logging_refactoring/ ) It has been broken into 5 projects Common-core Common-logging-jdk Common-logging-log4j Common-logging-spi Jbossxb Each of these projects builds a single jar. A maven build has been setup for each of these projects. The idea behind these changes is to cleanly separate each project into its own entity. After these changes are committed, binaries will be published to the repository for all projects and then they will be integrated to jbossAS/trunk. These changes apply only to the trunk version, not the 4.0 branch. Thoughts or concerns? Ruel Loehr JBoss QA -- -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.10.10/419 - Release Date: 8/15/2006

19 years, 10 months

4
5
0 / 0

jboss-4.0-testsuite-1.4 Build Completed With Testsuite Errors

by qa＠jboss.com

19 years, 10 months

1
0
0 / 0

jboss-remoting-testsuite-1.6 Build Completed With Testsuite Errors

by qa＠jboss.com

19 years, 10 months

1
0
0 / 0

jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors

by qa＠jboss.com

19 years, 10 months

1
0
0 / 0

jboss-3.2-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

19 years, 10 months

1
0
0 / 0

jboss-remoting-testsuite-1.4 Build Completed With Testsuite Errors

by qa＠jboss.com

19 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-development September 2006