You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Rick McGuire (JIRA)" <de...@geronimo.apache.org> on 2005/08/29 12:11:04 UTC
[jira] Created: (GERONIMO-940) Dual contribution code in Geronimo has pedigree questions.
Dual contribution code in Geronimo has pedigree questions.
----------------------------------------------------------
Key: GERONIMO-940
URL: http://issues.apache.org/jira/browse/GERONIMO-940
Project: Geronimo
Type: Bug
Components: common, kernel
Versions: 1.0-M5, 1.0
Environment: All
Reporter: Rick McGuire
There are a number of Geronimo classes that have also been contributed into the JBoss code base. These dual-contribution classes raise some pedigree and licensing conflict questions and should be replaced with cleanroom versions. Attached are cleanroom versions of the problem classes.
In addition to these replacement classes, the files in the packages org.apache.geronimo.system.url.file and org.apache.geronimo.system.url.resource also have a similar problem. However, these classes are not actually being used by Geronimo, and should just be removed rather than deleted. Removal of these requires a patch to GeronimoURLFactory, which is also attached. NOTE: The class GeronimoURLFactory has some JVM portability issues, and it's not clear that this URL factory is really required any more. If possible, it might be best to remove that class also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-940) Dual contribution code in Geronimo has pedigree questions.
Posted by "Geir Magnusson Jr (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-940?page=all ]
Geir Magnusson Jr reassigned GERONIMO-940:
------------------------------------------
Assign To: Geir Magnusson Jr
> Dual contribution code in Geronimo has pedigree questions.
> ----------------------------------------------------------
>
> Key: GERONIMO-940
> URL: http://issues.apache.org/jira/browse/GERONIMO-940
> Project: Geronimo
> Type: Bug
> Components: common, kernel
> Versions: 1.0-M4
> Environment: All
> Reporter: Rick McGuire
> Assignee: Geir Magnusson Jr
> Fix For: 1.0-M5
> Attachments: cleanroom.zip
>
> There are a number of Geronimo classes that have also been contributed into the JBoss code base. These dual-contribution classes raise some pedigree and licensing conflict questions and should be replaced with cleanroom versions. Attached are cleanroom versions of the problem classes.
> In addition to these replacement classes, the files in the packages org.apache.geronimo.system.url.file and org.apache.geronimo.system.url.resource also have a similar problem. However, these classes are not actually being used by Geronimo, and should just be removed rather than deleted. Removal of these requires a patch to GeronimoURLFactory, which is also attached. NOTE: The class GeronimoURLFactory has some JVM portability issues, and it's not clear that this URL factory is really required any more. If possible, it might be best to remove that class also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-940) Dual contribution code in Geronimo has pedigree questions.
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-940?page=all ]
Aaron Mulder updated GERONIMO-940:
----------------------------------
Fix Version: 1.0-M5
Version: 1.0-M4
(was: 1.0-M5)
(was: 1.0)
> Dual contribution code in Geronimo has pedigree questions.
> ----------------------------------------------------------
>
> Key: GERONIMO-940
> URL: http://issues.apache.org/jira/browse/GERONIMO-940
> Project: Geronimo
> Type: Bug
> Components: common, kernel
> Versions: 1.0-M4
> Environment: All
> Reporter: Rick McGuire
> Fix For: 1.0-M5
> Attachments: cleanroom.zip
>
> There are a number of Geronimo classes that have also been contributed into the JBoss code base. These dual-contribution classes raise some pedigree and licensing conflict questions and should be replaced with cleanroom versions. Attached are cleanroom versions of the problem classes.
> In addition to these replacement classes, the files in the packages org.apache.geronimo.system.url.file and org.apache.geronimo.system.url.resource also have a similar problem. However, these classes are not actually being used by Geronimo, and should just be removed rather than deleted. Removal of these requires a patch to GeronimoURLFactory, which is also attached. NOTE: The class GeronimoURLFactory has some JVM portability issues, and it's not clear that this URL factory is really required any more. If possible, it might be best to remove that class also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-940) Dual contribution code in Geronimo has pedigree questions.
Posted by "Rick McGuire (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-940?page=all ]
Rick McGuire updated GERONIMO-940:
----------------------------------
Attachment: cleanroom.zip
> Dual contribution code in Geronimo has pedigree questions.
> ----------------------------------------------------------
>
> Key: GERONIMO-940
> URL: http://issues.apache.org/jira/browse/GERONIMO-940
> Project: Geronimo
> Type: Bug
> Components: common, kernel
> Versions: 1.0-M5, 1.0
> Environment: All
> Reporter: Rick McGuire
> Attachments: cleanroom.zip
>
> There are a number of Geronimo classes that have also been contributed into the JBoss code base. These dual-contribution classes raise some pedigree and licensing conflict questions and should be replaced with cleanroom versions. Attached are cleanroom versions of the problem classes.
> In addition to these replacement classes, the files in the packages org.apache.geronimo.system.url.file and org.apache.geronimo.system.url.resource also have a similar problem. However, these classes are not actually being used by Geronimo, and should just be removed rather than deleted. Removal of these requires a patch to GeronimoURLFactory, which is also attached. NOTE: The class GeronimoURLFactory has some JVM portability issues, and it's not clear that this URL factory is really required any more. If possible, it might be best to remove that class also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-940) Dual contribution code in Geronimo has pedigree questions.
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-940?page=all ]
Dain Sundstrom closed GERONIMO-940:
-----------------------------------
Resolution: Fixed
Committed in Trunk and M5
Sending branches/1.0-M5/maven.xml
Sending branches/1.0-M5/modules/assembly/src/plan/client-system-plan.xml
Sending branches/1.0-M5/modules/assembly/src/plan/system-plan.xml
Sending branches/1.0-M5/modules/common/src/java/org/apache/geronimo/common/propertyeditor/BigDecimalEditor.java
Sending branches/1.0-M5/modules/common/src/java/org/apache/geronimo/common/propertyeditor/ClassEditor.java
Sending branches/1.0-M5/modules/common/src/java/org/apache/geronimo/common/propertyeditor/DateEditor.java
Sending branches/1.0-M5/modules/common/src/java/org/apache/geronimo/common/propertyeditor/PropertiesEditor.java
Sending branches/1.0-M5/modules/common/src/java/org/apache/geronimo/common/propertyeditor/PropertyEditorException.java
Sending branches/1.0-M5/modules/common/src/java/org/apache/geronimo/common/propertyeditor/PropertyEditors.java
Sending branches/1.0-M5/modules/common/src/java/org/apache/geronimo/common/propertyeditor/TextPropertyEditorSupport.java
Sending branches/1.0-M5/modules/common/src/java/org/apache/geronimo/common/propertyeditor/URLEditor.java
Adding branches/1.0-M5/modules/common/src/test/org/apache/geronimo/common/propertyeditor/URLEditorTest.java
Sending branches/1.0-M5/modules/kernel/src/java/org/apache/geronimo/kernel/ClassLoading.java
Sending branches/1.0-M5/modules/system/src/java/org/apache/geronimo/system/main/CommandLine.java
Sending branches/1.0-M5/modules/system/src/java/org/apache/geronimo/system/main/Daemon.java
Deleting branches/1.0-M5/modules/system/src/java/org/apache/geronimo/system/url
Deleting branches/1.0-M5/modules/system/src/test/org/apache/geronimo/system/url
Sending branches/1.0-M5/plugins/maven-geronimo-plugin/src/java/org/apache/geronimo/deployment/mavenplugin/StartServer.java
Sending trunk/maven.xml
Sending trunk/modules/assembly/src/plan/client-system-plan.xml
Sending trunk/modules/assembly/src/plan/system-plan.xml
Sending trunk/modules/common/src/java/org/apache/geronimo/common/propertyeditor/BigDecimalEditor.java
Sending trunk/modules/common/src/java/org/apache/geronimo/common/propertyeditor/ClassEditor.java
Sending trunk/modules/common/src/java/org/apache/geronimo/common/propertyeditor/DateEditor.java
Sending trunk/modules/common/src/java/org/apache/geronimo/common/propertyeditor/PropertiesEditor.java
Sending trunk/modules/common/src/java/org/apache/geronimo/common/propertyeditor/PropertyEditorException.java
Sending trunk/modules/common/src/java/org/apache/geronimo/common/propertyeditor/PropertyEditors.java
Sending trunk/modules/common/src/java/org/apache/geronimo/common/propertyeditor/TextPropertyEditorSupport.java
Sending trunk/modules/common/src/java/org/apache/geronimo/common/propertyeditor/URLEditor.java
Adding trunk/modules/common/src/test/org/apache/geronimo/common/propertyeditor/URLEditorTest.java
Sending trunk/modules/kernel/src/java/org/apache/geronimo/kernel/ClassLoading.java
Sending trunk/modules/system/src/java/org/apache/geronimo/system/main/CommandLine.java
Sending trunk/modules/system/src/java/org/apache/geronimo/system/main/Daemon.java
Deleting trunk/modules/system/src/java/org/apache/geronimo/system/url/DelegatingURLConnection.java
Deleting trunk/modules/system/src/java/org/apache/geronimo/system/url/GeronimoURLFactory.java
Deleting trunk/modules/system/src/java/org/apache/geronimo/system/url/file
Deleting trunk/modules/system/src/java/org/apache/geronimo/system/url/resource
Deleting trunk/modules/system/src/test/org/apache/geronimo/system/url
Sending trunk/plugins/maven-geronimo-plugin/src/java/org/apache/geronimo/deployment/mavenplugin/StartServer.java
Transmitting file data ................................
Committed revision 290873.
> Dual contribution code in Geronimo has pedigree questions.
> ----------------------------------------------------------
>
> Key: GERONIMO-940
> URL: http://issues.apache.org/jira/browse/GERONIMO-940
> Project: Geronimo
> Type: Bug
> Components: common, kernel
> Versions: 1.0-M4
> Environment: All
> Reporter: Rick McGuire
> Assignee: Dain Sundstrom
> Fix For: 1.0-M5
> Attachments: cleanroom.zip
>
> There are a number of Geronimo classes that have also been contributed into the JBoss code base. These dual-contribution classes raise some pedigree and licensing conflict questions and should be replaced with cleanroom versions. Attached are cleanroom versions of the problem classes.
> In addition to these replacement classes, the files in the packages org.apache.geronimo.system.url.file and org.apache.geronimo.system.url.resource also have a similar problem. However, these classes are not actually being used by Geronimo, and should just be removed rather than deleted. Removal of these requires a patch to GeronimoURLFactory, which is also attached. NOTE: The class GeronimoURLFactory has some JVM portability issues, and it's not clear that this URL factory is really required any more. If possible, it might be best to remove that class also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-940) Dual contribution code in Geronimo has pedigree questions.
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-940?page=all ]
Dain Sundstrom reassigned GERONIMO-940:
---------------------------------------
Assign To: Dain Sundstrom (was: Geir Magnusson Jr)
> Dual contribution code in Geronimo has pedigree questions.
> ----------------------------------------------------------
>
> Key: GERONIMO-940
> URL: http://issues.apache.org/jira/browse/GERONIMO-940
> Project: Geronimo
> Type: Bug
> Components: common, kernel
> Versions: 1.0-M4
> Environment: All
> Reporter: Rick McGuire
> Assignee: Dain Sundstrom
> Fix For: 1.0-M5
> Attachments: cleanroom.zip
>
> There are a number of Geronimo classes that have also been contributed into the JBoss code base. These dual-contribution classes raise some pedigree and licensing conflict questions and should be replaced with cleanroom versions. Attached are cleanroom versions of the problem classes.
> In addition to these replacement classes, the files in the packages org.apache.geronimo.system.url.file and org.apache.geronimo.system.url.resource also have a similar problem. However, these classes are not actually being used by Geronimo, and should just be removed rather than deleted. Removal of these requires a patch to GeronimoURLFactory, which is also attached. NOTE: The class GeronimoURLFactory has some JVM portability issues, and it's not clear that this URL factory is really required any more. If possible, it might be best to remove that class also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira