[JBoss JIRA] (WFCORE-563) Upgrade to Xerces 2.11.0.SP3
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-563?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-563:
------------------------------------------------
Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1148739|https://bugzilla.redhat.com/show_bug.cgi?id=1148739] from NEW to CLOSED
> Upgrade to Xerces 2.11.0.SP3
> ----------------------------
>
> Key: WFCORE-563
> URL: https://issues.jboss.org/browse/WFCORE-563
> Project: WildFly Core
> Issue Type: Component Upgrade
> Affects Versions: 1.0.0.Alpha19
> Environment: WildFly 8.1.0.Final, JDK 7, Ubuntu, Windows, Mac OS
> Reporter: Carlos Barragan
> Assignee: Carlo de Wolf
> Priority: Critical
> Fix For: 1.0.0.Beta1
>
> Attachments: stacktrace.txt
>
>
> Xerces 2.9.1 has a bug when parsing Times with "24" hrs.
> {code}
> DatatypeFactory.newInstance().newXMLGregorianCalendar("24:00:00Z");
> {code}
> We have this problem in one of our web services because we get request with the above time format.
> Xerces 2.11.0 does not contain that bug.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4409) java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy. It's not clear what's the reason of the problem from the log
by Alexandr Sokolov (JIRA)
[ https://issues.jboss.org/browse/WFLY-4409?page=com.atlassian.jira.plugin.... ]
Alexandr Sokolov updated WFLY-4409:
-----------------------------------
Description:
In the log during the application server startup we see in the log file:
{code}
[0m[31m15:10:25,997 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.subunit."mms.ear"."webservices.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."mms.ear"."webservices.jar".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment "webservices.jar" of deployment "mms.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72) [rt.jar:1.8.0_25]
at java.lang.Class.createAnnotationData(Class.java:3513) [rt.jar:1.8.0_25]
at java.lang.Class.annotationData(Class.java:3502) [rt.jar:1.8.0_25]
at java.lang.Class.getAnnotation(Class.java:3407) [rt.jar:1.8.0_25]
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getRemoteBusinessInterfaces(BusinessViewAnnotationProcessor.java:148)
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.processViewAnnotations(BusinessViewAnnotationProcessor.java:116)
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:90)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
... 5 more
...
[0m[31m15:10:27,315 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "mms.ear")]) - failure description: {
"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"mms.ear\".\"webservices.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"mms.ear\".\"webservices.jar\".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment \"webservices.jar\" of deployment \"mms.ear\"
Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy"},
"JBAS014771: Services with missing/unavailable dependencies" => [
"jboss.deployment.unit.\"mms.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"mms.ear\".beanmanager]",
"jboss.naming.context.java.comp.mms.wp.TemplateVariableService.Validator is missing [jboss.naming.context.java.comp.mms.wp.TemplateVariableService]",
"jboss.naming.context.java.comp.mms.configuration.GenericDao.InAppClientContainer is missing [jboss.naming.context.java.comp.mms.configuration.GenericDao]",
"jboss.naming.context.java.comp.mms.mmsServiceEJB.MMSMagnoliaSSOService.ORB is missing [jboss.naming.context.java.comp.mms.mmsServiceEJB.MMSMagnoliaSSOService]",
...
{code}
>From this output it's not clear what exactly is absent in the ear file.
Could you refactor logging for this error. In order to display which exactly annotation was not found.
was:
In the log during the application server startup we see in the log file:
{code}
[0m[31m15:10:25,997 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.subunit."mms.ear"."webservices.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."mms.ear"."webservices.jar".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment "webservices.jar" of deployment "mms.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72) [rt.jar:1.8.0_25]
at java.lang.Class.createAnnotationData(Class.java:3513) [rt.jar:1.8.0_25]
at java.lang.Class.annotationData(Class.java:3502) [rt.jar:1.8.0_25]
at java.lang.Class.getAnnotation(Class.java:3407) [rt.jar:1.8.0_25]
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getRemoteBusinessInterfaces(BusinessViewAnnotationProcessor.java:148)
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.processViewAnnotations(BusinessViewAnnotationProcessor.java:116)
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:90)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
... 5 more
...
[0m[31m15:10:27,315 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "mms.ear")]) - failure description: {
"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"mms.ear\".\"webservices.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"mms.ear\".\"webservices.jar\".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment \"webservices.jar\" of deployment \"mms.ear\"
Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy"},
"JBAS014771: Services with missing/unavailable dependencies" => [
"jboss.deployment.unit.\"mms.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"mms.ear\".beanmanager]",
"jboss.naming.context.java.comp.mms.wp.TemplateVariableService.Validator is missing [jboss.naming.context.java.comp.mms.wp.TemplateVariableService]",
"jboss.naming.context.java.comp.mms.configuration.GenericDao.InAppClientContainer is missing [jboss.naming.context.java.comp.mms.configuration.GenericDao]",
"jboss.naming.context.java.comp.mms.mmsServiceEJB.MMSMagnoliaSSOService.ORB is missing [jboss.naming.context.java.comp.mms.mmsServiceEJB.MMSMagnoliaSSOService]",
...
{code}
>From this output it's not clear what exactly is absent in the ear file.
Could you refactore logging for this error. In order to display which exactly annotation was not found.
> java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy. It's not clear what's the reason of the problem from the log
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4409
> URL: https://issues.jboss.org/browse/WFLY-4409
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 8.2.0.Final
> Reporter: Alexandr Sokolov
> Assignee: Jason Greene
>
> In the log during the application server startup we see in the log file:
> {code}
> [0m[31m15:10:25,997 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.subunit."mms.ear"."webservices.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."mms.ear"."webservices.jar".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment "webservices.jar" of deployment "mms.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
> at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72) [rt.jar:1.8.0_25]
> at java.lang.Class.createAnnotationData(Class.java:3513) [rt.jar:1.8.0_25]
> at java.lang.Class.annotationData(Class.java:3502) [rt.jar:1.8.0_25]
> at java.lang.Class.getAnnotation(Class.java:3407) [rt.jar:1.8.0_25]
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getRemoteBusinessInterfaces(BusinessViewAnnotationProcessor.java:148)
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.processViewAnnotations(BusinessViewAnnotationProcessor.java:116)
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:90)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
> ... 5 more
> ...
> [0m[31m15:10:27,315 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "mms.ear")]) - failure description: {
> "JBAS014671: Failed services" => {"jboss.deployment.subunit.\"mms.ear\".\"webservices.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"mms.ear\".\"webservices.jar\".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment \"webservices.jar\" of deployment \"mms.ear\"
> Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy"},
> "JBAS014771: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"mms.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"mms.ear\".beanmanager]",
> "jboss.naming.context.java.comp.mms.wp.TemplateVariableService.Validator is missing [jboss.naming.context.java.comp.mms.wp.TemplateVariableService]",
> "jboss.naming.context.java.comp.mms.configuration.GenericDao.InAppClientContainer is missing [jboss.naming.context.java.comp.mms.configuration.GenericDao]",
> "jboss.naming.context.java.comp.mms.mmsServiceEJB.MMSMagnoliaSSOService.ORB is missing [jboss.naming.context.java.comp.mms.mmsServiceEJB.MMSMagnoliaSSOService]",
> ...
> {code}
> From this output it's not clear what exactly is absent in the ear file.
> Could you refactor logging for this error. In order to display which exactly annotation was not found.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4409) java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy. It's not clear what's the reason of the problem from the log
by Alexandr Sokolov (JIRA)
Alexandr Sokolov created WFLY-4409:
--------------------------------------
Summary: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy. It's not clear what's the reason of the problem from the log
Key: WFLY-4409
URL: https://issues.jboss.org/browse/WFLY-4409
Project: WildFly
Issue Type: Bug
Affects Versions: 8.2.0.Final
Reporter: Alexandr Sokolov
Assignee: Jason Greene
In the log during the application server startup we see in the log file:
{code}
[0m[31m15:10:25,997 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.subunit."mms.ear"."webservices.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."mms.ear"."webservices.jar".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment "webservices.jar" of deployment "mms.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120) [rt.jar:1.8.0_25]
at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72) [rt.jar:1.8.0_25]
at java.lang.Class.createAnnotationData(Class.java:3513) [rt.jar:1.8.0_25]
at java.lang.Class.annotationData(Class.java:3502) [rt.jar:1.8.0_25]
at java.lang.Class.getAnnotation(Class.java:3407) [rt.jar:1.8.0_25]
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getRemoteBusinessInterfaces(BusinessViewAnnotationProcessor.java:148)
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.processViewAnnotations(BusinessViewAnnotationProcessor.java:116)
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:90)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
... 5 more
...
[0m[31m15:10:27,315 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "mms.ear")]) - failure description: {
"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"mms.ear\".\"webservices.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"mms.ear\".\"webservices.jar\".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment \"webservices.jar\" of deployment \"mms.ear\"
Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy"},
"JBAS014771: Services with missing/unavailable dependencies" => [
"jboss.deployment.unit.\"mms.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"mms.ear\".beanmanager]",
"jboss.naming.context.java.comp.mms.wp.TemplateVariableService.Validator is missing [jboss.naming.context.java.comp.mms.wp.TemplateVariableService]",
"jboss.naming.context.java.comp.mms.configuration.GenericDao.InAppClientContainer is missing [jboss.naming.context.java.comp.mms.configuration.GenericDao]",
"jboss.naming.context.java.comp.mms.mmsServiceEJB.MMSMagnoliaSSOService.ORB is missing [jboss.naming.context.java.comp.mms.mmsServiceEJB.MMSMagnoliaSSOService]",
...
{code}
>From this output it's not clear what exactly is absent in the ear file.
Could you refactore logging for this error. In order to display which exactly annotation was not found.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (DROOLS-656) The blessed repo's should not accept a git force push
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-656?page=com.atlassian.jira.plugin... ]
Geoffrey De Smet commented on DROOLS-656:
-----------------------------------------
mbiarnes, would you mind creating a new repo under droolsjbpm, push some stuff to it and then force push some more stuff to it? That will answer the question above.
Note: We can't on existing repo's without potentially breaking them which is not an option.
> The blessed repo's should not accept a git force push
> -----------------------------------------------------
>
> Key: DROOLS-656
> URL: https://issues.jboss.org/browse/DROOLS-656
> Project: Drools
> Issue Type: Task
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
> Priority: Critical
>
> If someone ever git forces pushes to a blessed repo all hell will break loose.
> We can prevent git forces pushes, as explained here:
> http://stackoverflow.com/questions/1754491/is-there-a-way-to-configure-gi...
> Force pushing on blessed repo's is very bad, but force pushing on forks is very common.
> Requirements:
> - Enable this on 1 new dummy blessed repository
> - Prove you cannot force push to
> - Prove you can fork it and force push to your fork.
> - Delete the dummy blessed repository
> - If that works well, enable it on the real blessed repositories
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (DROOLS-656) The blessed repo's should not accept a git force push
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-656?page=com.atlassian.jira.plugin... ]
Geoffrey De Smet edited comment on DROOLS-656 at 3/6/15 2:34 AM:
-----------------------------------------------------------------
Yes, James Dennes (Github Staff) told me it's done on all repo's of https://github.com/droolsjbpm on all branches (but not forks of course) on 20-JAN-2015.
No idea if it automatically applies to new repo's in that same github organization...
was (Author: ge0ffrey):
Yes, James Dennes told me it's done on all repo's of https://github.com/droolsjbpm on all branches (but not forks of course) on 20-JAN-2015.
No idea if it automatically applies to new repo's in that same github organization...
> The blessed repo's should not accept a git force push
> -----------------------------------------------------
>
> Key: DROOLS-656
> URL: https://issues.jboss.org/browse/DROOLS-656
> Project: Drools
> Issue Type: Task
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
> Priority: Critical
>
> If someone ever git forces pushes to a blessed repo all hell will break loose.
> We can prevent git forces pushes, as explained here:
> http://stackoverflow.com/questions/1754491/is-there-a-way-to-configure-gi...
> Force pushing on blessed repo's is very bad, but force pushing on forks is very common.
> Requirements:
> - Enable this on 1 new dummy blessed repository
> - Prove you cannot force push to
> - Prove you can fork it and force push to your fork.
> - Delete the dummy blessed repository
> - If that works well, enable it on the real blessed repositories
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (DROOLS-491) drools-karaf-features should avoid declaring its own dependency versions
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-491?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer resolved DROOLS-491.
-------------------------------------------
Resolution: Done
the used versions are the one from jboss-ip-bom:
<karaf.version.org.apache.camel>${version.org.apache.camel}</karaf.version.org.apache.camel>
<karaf.version.org.apache.cxf>${version.org.apache.cxf}</karaf.version.org.apache.cxf>
<karaf.version.org.apache.helix>${version.org.apache.helix}</karaf.version.org.apache.helix>
<karaf.version.com.google.protobuf>${version.com.google.protobuf}</karaf.version.com.google.protobuf>
<karaf.version.joda-time>${version.joda-time}</karaf.version.joda-time>
<karaf.version.org.jboss.solder>${version.org.jboss.solder}</karaf.version.org.jboss.solder>
<karaf.version.org.jboss.seam>${version.org.jboss.seam}</karaf.version.org.jboss.seam>
<karaf.version.org.jboss.weld>${version.org.jboss.weld.weld}</karaf.version.org.jboss.weld>
<karaf.version.org.mvel>${version.org.mvel}</karaf.version.org.mvel>
<karaf.version.javax.enterprise.cdi>${version.javax.enterprise}</karaf.version.javax.enterprise.cdi>
> drools-karaf-features should avoid declaring its own dependency versions
> ------------------------------------------------------------------------
>
> Key: DROOLS-491
> URL: https://issues.jboss.org/browse/DROOLS-491
> Project: Drools
> Issue Type: Task
> Affects Versions: 6.1.0.Beta3
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
>
> At the top of this file:
> https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/drools-o...
> We find:
> {code}
> <!-- Normal reuses -->
> <!-- TODO Because these properties moved into the jboss-integration-platform-bom, we can't use them directly: -->
> <!--<karaf.version.org.apache.camel>${version.org.apache.camel}</karaf.version.org.apache.camel>-->
> <!--<karaf.version.org.apache.cxf>${version.org.apache.cxf}</karaf.version.org.apache.cxf>-->
> <!--<karaf.version.org.apache.helix>${version.org.apache.helix}</karaf.version.org.apache.helix>-->
> <!--<karaf.version.com.google.protobuf>${version.com.google.protobuf}</karaf.version.com.google.protobuf>-->
> <!--<karaf.version.joda-time>${version.joda-time}</karaf.version.joda-time>-->
> <!--<karaf.version.org.jboss.solder>${version.org.jboss.solder}</karaf.version.org.jboss.solder>-->
> <!--<karaf.version.org.jboss.seam>${version.org.jboss.seam}</karaf.version.org.jboss.seam>-->
> <!--<karaf.version.org.jboss.weld>${version.org.jboss.weld}</karaf.version.org.jboss.weld>-->
> <!--<karaf.version.org.mvel>${version.org.mvel}</karaf.version.org.mvel>-->
> <!-- TODO Instead of hard coding them and using maven filtering, we should use the karaf features-maven-plugin -->
> <karaf.version.org.apache.camel>2.10.3</karaf.version.org.apache.camel>
> <karaf.version.org.apache.cxf>2.6.6</karaf.version.org.apache.cxf>
> <karaf.version.org.apache.helix>0.6.1-incubating</karaf.version.org.apache.helix>
> <karaf.version.com.google.protobuf>2.5.0</karaf.version.com.google.protobuf>
> <karaf.version.joda-time>1.6.2</karaf.version.joda-time>
> <karaf.version.org.jboss.solder>3.2.0.Final</karaf.version.org.jboss.solder>
> <karaf.version.org.jboss.seam>3.1.0.Final</karaf.version.org.jboss.seam>
> <karaf.version.org.jboss.weld>1.1.13.Final</karaf.version.org.jboss.weld>
> <karaf.version.org.mvel>2.1.6.Final</karaf.version.org.mvel>
> {code}
> That TODO "TODO Because these properties moved into the jboss-integration-platform-bom, we can't use them directly" is *no longer valid*. We now have the jboss-integration-platform-parent as a parent, so we do have those versions available, so there's no need to hardcode those versions.
> As for the other versions
> {code}
> <!-- Overwrites with a different Maven version -->
> <karaf.version.commons-codec>1.7</karaf.version.commons-codec>
> <karaf.version.javax.enterprise.cdi>1.0-SP4</karaf.version.javax.enterprise.cdi>
> <karaf.version.javax.inject>1.0</karaf.version.javax.inject>
> <karaf.version.org.codehaus.janino>2.6.1</karaf.version.org.codehaus.janino>
> <karaf.version.org.eclipse.jdt.core.compiler>4.2.1</karaf.version.org.eclipse.jdt.core.compiler>
> <!-- Overwrites with a servicemix version -->
> <karaf.servicemix.version.com.google.protobuf>2.4.1_1</karaf.servicemix.version.com.google.protobuf>
> <karaf.servicemix.version.com.sun.xml.bind.jaxb>2.2.1.1_2</karaf.servicemix.version.com.sun.xml.bind.jaxb>
> <karaf.servicemix.version.com.thoughtworks.xstream>1.4.3_1</karaf.servicemix.version.com.thoughtworks.xstream>
> <karaf.servicemix.version.javax.xml.bind.jaxb>1.9.0</karaf.servicemix.version.javax.xml.bind.jaxb>
> <karaf.servicemix.version.org.antlr>3.5_1</karaf.servicemix.version.org.antlr>
> <karaf.servicemix.version.org.apache.poi>3.9_2</karaf.servicemix.version.org.apache.poi>
> <karaf.servicemix.version.org.codehaus.woodstox>3.2.9_3</karaf.servicemix.version.org.codehaus.woodstox>
> <karaf.servicemix.version.org.quartz-scheduler>2.1.6_1</karaf.servicemix.version.org.quartz-scheduler>
> <!-- Specs -->
> <karaf.servicemix.version.scripting-api>2.4.0</karaf.servicemix.version.scripting-api>
> <!-- Special overwrites -->
> <karaf.version.org.apache.aries.jpa>1.0.1</karaf.version.org.apache.aries.jpa>
> {code}
> figure out if any of those can be removed from being hard coded...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months