Create a process for uploading jboss app server jars into the maven repository.
-------------------------------------------------------------------------------
Key: JBBUILD-468
URL: http://jira.jboss.com/jira/browse/JBBUILD-468
Project: JBoss Build System
Issue Type: Task
Components: Maven
Reporter: Paul Gier
Fix For: Maven Build - Maint 2008
The jboss app server releases should be available in the maven repository. There should be a simple process (including standard groupIds and artifactIds) for uploading these jar when the app server is released.
--
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
adding options to a web decision table has no effect
----------------------------------------------------
Key: JBRULES-1848
URL: https://jira.jboss.org/jira/browse/JBRULES-1848
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-guvnor
Affects Versions: 5.0.0.M2
Environment: Linux, Jboss 4.2.2
Reporter: Nicolas Heron
Assignee: Mark Proctor
When adding an option to a web decision able, it has no effect on the generated rule.
The biggest inconvenient is when using ruleflow
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Add missing md5/sha1 checksums to repository.jboss.org
------------------------------------------------------
Key: JBBUILD-387
URL: http://jira.jboss.com/jira/browse/JBBUILD-387
Project: JBoss Build System
Issue Type: Task
Components: Maven
Reporter: Paul Gier
Assigned To: Paul Gier
Fix For: Maven Build - Maint 2007
Several of the artifacts currently in the repository are missing the maven generated checksums. This causes warning messages to be displayed during builds. These checksums should be generated and added to the repository.
--
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
Look into combining default pom and jdk14 poms.
-----------------------------------------------
Key: JBBUILD-424
URL: http://jira.jboss.com/jira/browse/JBBUILD-424
Project: JBoss Build System
Issue Type: Task
Components: Maven
Reporter: Paul Gier
Fix For: Maven Build - Maint 2007
Having separate pom files (default and jdk14) is causing some problems with releases. Maybe the poms can be combined using profiles so that we don't have to keep two separate poms up to date.
I had some issues when attempting to use profiles before:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=115157
But I think that I can get around those issues now.
--
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
Set up retro jdk1.4 build and test of microcontainer on hudson.
---------------------------------------------------------------
Key: JBBUILD-410
URL: http://jira.jboss.com/jira/browse/JBBUILD-410
Project: JBoss Build System
Issue Type: Task
Components: Maven
Reporter: Paul Gier
Fix For: Maven Build - App Server
A retro build of microcontainer should be set up on hudson so that we can see which tests are failing.
--
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
Fix microcontainer jdk14 tests.
-------------------------------
Key: JBBUILD-409
URL: http://jira.jboss.com/jira/browse/JBBUILD-409
Project: JBoss Build System
Issue Type: Task
Components: JBossRetro, Maven
Reporter: Paul Gier
Fix For: Maven Build - App Server
Many of the retro build tests for microcontainer are failing. These are mostly caused by missing features of jboss-retro. Once the relevant retro issues have been resolved, the tests should be checked again to find remaining issues.
--
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
Research issue with microcontainer kernel retro builds
------------------------------------------------------
Key: JBBUILD-405
URL: http://jira.jboss.com/jira/browse/JBBUILD-405
Project: JBoss Build System
Issue Type: Task
Components: JBossRetro, Maven
Reporter: Paul Gier
Fix For: Maven Build - Maint 2007
The microcontainer kernel is not able to compile with dependency on retroed version of jboss-container. It compiles ok depending on the regular container, but with the retro container, there is a problem with the annotations.
--
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
Getting wrong version of a transitive dependency
------------------------------------------------
Key: JBBUILD-443
URL: http://jira.jboss.com/jira/browse/JBBUILD-443
Project: JBoss Build System
Issue Type: Bug
Components: Maven
Reporter: Carlo de Wolf
jboss-ejb3-core depends on jboss-metadata 1.0.0.Beta4
jboss-metadata 1.0.0.Beta4 depends on jboss-container 2.0.0.Beta6
but jboss-container SNAPSHOT is used instead.
--
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
Update org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase
---------------------------------------------------------------------
Key: JBAS-5872
URL: https://jira.jboss.org/jira/browse/JBAS-5872
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Dimitris Andreadis
Assignee: Shelly McGowan
Fix For: JBossAS-5.0.0.GA
org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase needs updating.
There should be a new test testJavaEE50Compatibility.
I don't we need to keep testJ2EERI141Compatibility.
And we should be testing against 4.2.x SerialVersionUIDs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira