March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBBUILD-196) modification of version info in jar manifests

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-196?page=all ] Paul Gier closed JBBUILD-196. ----------------------------- Resolution: Out of Date Similar functionality should be provided once we migrate to maven. > modification of version info in jar manifests > --------------------------------------------- > > Key: JBBUILD-196 > URL: http://jira.jboss.com/jira/browse/JBBUILD-196 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: Ruel Loehr > > > A common utility that pulls this info from the java.lang.Package > > version info coming from the standard version jar manifest headers is > > what I would like to see us move to. The way the jbossas dists are > > processed is that any jar version info that exists is preserved, but > > anything missing is overriden with the jbossas version info. Utimately > > this needs to all tie out to the component-info.xml and jar manifests. > > Another mbean tool I want is one which generates a graph of all > > component versions with their dependencies, so this requires > > additional jar headers or dependency descriptor. > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBBUILD-165) SerailVersion UID testing

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-165?page=all ] Paul Gier closed JBBUILD-165. ----------------------------- Resolution: Out of Date > SerailVersion UID testing > ------------------------- > > Key: JBBUILD-165 > URL: http://jira.jboss.com/jira/browse/JBBUILD-165 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: Ruel Loehr > > We need to create a jbossbuild task that is a variation of the SerialVersionUIDUnitTestCase utilities that can be run on an output dir to identify every serializable class that lacks an explicit serialVersionUID. There should not be any project binaries in the repository that have such floating serialVersionUIDs as this is resulting in incompatible versions where these classes are being exchanged across versions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBBUILD-71) Generate FileSets Artifacts and Sources

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-71?page=all ] Paul Gier closed JBBUILD-71. ---------------------------- Resolution: Out of Date > Generate FileSets Artifacts and Sources > --------------------------------------- > > Key: JBBUILD-71 > URL: http://jira.jboss.com/jira/browse/JBBUILD-71 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: Ryan Campbell > Fix For: JBossBuild-1.1 RC1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > It should be possible to refer to jbossbuild artifacts and sources in the build file outside of the componentdef. This will allow components to have adhoc non-generated targets, which refer to the declared classpaths within the componentdef. > For instance a <source id="tests"/> would generate an ant FileSet with an id of pathelements.test which would contain all the contents of the <pathElements/> macro. A target could then reference this FileSet for arbitrary purposes. > This could simply be done in a new targetdef which the adhoc component targets depend on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBBUILD-75) Need a better overview document on interaction of targets/tasks/types

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-75?page=all ] Paul Gier closed JBBUILD-75. ---------------------------- Resolution: Out of Date > Need a better overview document on interaction of targets/tasks/types > --------------------------------------------------------------------- > > Key: JBBUILD-75 > URL: http://jira.jboss.com/jira/browse/JBBUILD-75 > Project: JBoss Build System > Issue Type: Task > Components: Targets and Tasks > Reporter: Scott M Stark > > So in going through the build system as part of looking into the component-info.xml dependency issue I am finding the interaction between ant task/types, jboss task/types and how the composition of build.xml/tasks.xml/component-info.xml results in a build process difficult to pull together. We need an overview doc that starts from build.xml and defines: > - every jbossbuild element that can be used > - how it is created (custom task, custom type, tasks.xml macro, etc.) > - the relationship between elements > The current docs on the build system don't cover sufficient detail to allow for customization of the build system. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBBUILD-63) Bootstrap jbossbuild from repository

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-63?page=all ] Paul Gier closed JBBUILD-63. ---------------------------- Resolution: Out of Date There is another issue (JBBUILD-202) to provide the bootstrap functionality with maven. > Bootstrap jbossbuild from repository > ------------------------------------ > > Key: JBBUILD-63 > URL: http://jira.jboss.com/jira/browse/JBBUILD-63 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: Ryan Campbell > Fix For: JBossBuild-1.1 RC1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Currently, jbossbuild is stored in the tools project in CVS. In order for projects not in this CVS repository to use jbossbuild, they would likewise need to store jbossbuild artifacts (jbossbuild.jar, tasks.xml, jbossbuild.properties) in their cvs repositories. An alternative to this is to make jbossbuild a component in repository.jboss.com. > The chicken and the egg: Projects could then have a boostrap.xml which could download jbossbuild as part of the synchronize process, or a special bootstrap target. The nice thing about this is that projects could easily upgrade to a new version of jbossbuild. > This also eliminates the need for cvs aliases. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBBUILD-67) Detect Duplicate artifactdefs

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-67?page=all ] Paul Gier closed JBBUILD-67. ---------------------------- Resolution: Out of Date > Detect Duplicate artifactdefs > ----------------------------- > > Key: JBBUILD-67 > URL: http://jira.jboss.com/jira/browse/JBBUILD-67 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: Ryan Campbell > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > If I accidently create two artifactdefs for the same artifact: > <artifactdef artifact="foo.jar"/> > <artifactdef artifact="foo.jar"/> > jbossbuild will simply overwrite the first jar with the second when building. Instead, I should recieve an error: "Duplicate ArtifactDefinition: foo.jar" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBBUILD-68) Version Incompatibility

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-68?page=all ] Paul Gier closed JBBUILD-68. ---------------------------- Resolution: Out of Date > Version Incompatibility > ----------------------- > > Key: JBBUILD-68 > URL: http://jira.jboss.com/jira/browse/JBBUILD-68 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: Ryan Campbell > > Now that multiple standalone JBoss components will be included into the build, there is a risk that their thirdparty dependencies will diverge. i.e., that remoting and cache will depend on incompatible versions of jgroups. I'm putting this as a JIRA task until we are ready to discuss it in the forums. > A basic solution would be to encode the version of the 3rd party jar that the jboss jar was compiled with in the manifest: > jboss-remoting.jar/META-INF/MANIFEST.MF: > JBossBuild-Compatibilities: jgroups.jar=2.2.8RC1 > So, if jboss-remoting.jar was included in a release with something besides jgroups 2.2.*, the build would produce an error. > A fancier impl would would allow a component to define multiple comptabilities in its build file: > <depends component="jgroups-jgroups"> > <compatible version="2.2.*"/> > <compatible version="2.3.*"/> > </depends> > The above supports the likelihood that one version of remoting is compatible with multiple versions of jgroups. However, its weakness is that there is an equal likelihood that remoting will at some point become incompatible with jgroups 2.2.*. Not withstanding some mechanism to test/enforce the compatibility declaration? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBBUILD-10) Add Code Coverage

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-10?page=all ] Paul Gier updated JBBUILD-10: ----------------------------- Fix Version/s: MavenBuild 2.0 We can look at putting this in the maven builds. > Add Code Coverage > ----------------- > > Key: JBBUILD-10 > URL: http://jira.jboss.com/jira/browse/JBBUILD-10 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: Ryan Campbell > Fix For: MavenBuild 2.0 > > > Allow a component to generate unit test code coverage reports. > Look at using Clover for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBBUILD-5) Add Ant task to modify 3rd party jar manifests

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-5?page=comments#action_12356930 ] Paul Gier commented on JBBUILD-5: --------------------------------- I believe this issue is out of date. Can I close this? > Add Ant task to modify 3rd party jar manifests > ---------------------------------------------- > > Key: JBBUILD-5 > URL: http://jira.jboss.com/jira/browse/JBBUILD-5 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: Ryan Campbell > > We need to find/build a task to modify 3rd party jar manifests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBBUILD-74) Validatable Build Files

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-74?page=all ] Paul Gier updated JBBUILD-74: ----------------------------- Fix Version/s: jboss-deploy-maven-plugin-1.2.GA (was: JBossBuild-1.1 RC1) Assignee: Paul Gier I would like to create an xsd for component-info.xml to be used by the jboss-deploy-maven-plugin > Validatable Build Files > ----------------------- > > Key: JBBUILD-74 > URL: http://jira.jboss.com/jira/browse/JBBUILD-74 > Project: JBoss Build System > Issue Type: Feature Request > Affects Versions: JBossBuild-1.1 DR1 > Reporter: Ryan Campbell > Assigned To: Paul Gier > Fix For: jboss-deploy-maven-plugin-1.2.GA > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Create xsd schemas for the component, componentdef, and build elements so that developers can validate their component-info.xml and jbossbuild.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 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-jira March 2007