November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-284) Rewrite CLI FileArgumentTestCase

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-284: ---------------------------------------- Summary: Rewrite CLI FileArgumentTestCase Key: WFCORE-284 URL: https://issues.jboss.org/browse/WFCORE-284 Project: WildFly Core Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky The test has been failing sporadically for awhile. One of the problems is to figure out the conditions under which the test fails. They haven't been determined so far. Perhaps, attempts to simplify and clean up the logic in the test will help. The test is org.jboss.as.test.integration.management.cli.FileArgumentTestCase -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-146) Use .gitattributes to force linux line endings for all text files

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-146?page=com.atlassian.jira.plugin... ] Geoffrey De Smet reassigned DROOLS-146: --------------------------------------- Assignee: Michael Biarnes Kiefer (was: Geoffrey De Smet) This has worked well for months on the optaplanner repository. Michael, 1) All the other blessed repositories should now also get that .gitattributes file (copy it for the optaplanner repo). Possibly improve it first before copying. 2) Clean up all previous errors, as stated in the important above. Shells scripts like dos2unix etc can help here. All java files etc were dos2unixed 2 years ago, but we've seen many contributions since then ... > Use .gitattributes to force linux line endings for all text files > ----------------------------------------------------------------- > > Key: DROOLS-146 > URL: https://issues.jboss.org/browse/DROOLS-146 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > > With .gitattributes we can force all java files etc to have linux file endings. > I am experimenting with this in the optaplanner repository: > https://github.com/droolsjbpm/optaplanner/commit/40dca629262568d5e5abb379... > If it works well, we'll want to compile a good overall .gitattributes file and commit it to all droolsjbpm repositories. > During the refactor to .gitattributes, execute this script to detect and fix all previous errors: > https://help.github.com/articles/dealing-with-line-endings#re-normalizing... > *Important:* > In OptaPlanner we just committed the file without "fixing all previous errors". It turned out we had 2. > The person who adds the .gitattributes file doesn't get a problem, but other people who clone a new repository > get immediate modifications to incorrect files. This is a PITA. > So *after the commit .gitattributes files, all previous errors need to be fixed for and verified by doing a new clone and a git status on that new clone.* -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-305) No file name information in detail error when compiling the java file

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-305?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWEB-305: ----------------------------------------------- Radim Hatlapatka <rhatlapa(a)redhat.com> changed the Status of [bug 1155635|https://bugzilla.redhat.com/show_bug.cgi?id=1155635] from ON_QA to VERIFIED > No file name information in detail error when compiling the java file > ---------------------------------------------------------------------- > > Key: JBWEB-305 > URL: https://issues.jboss.org/browse/JBWEB-305 > Project: JBoss Web > Issue Type: Bug > Affects Versions: JBossWeb-7.4.0.GA, JBossWeb-7.5.0.GA > Reporter: Aaron Ogburn > Assignee: Remy Maucherat > Priority: Minor > > JBossWeb does not have a fix to https://issues.apache.org/bugzilla/show_bug.cgi?id=54466. Helpful file name information can be left off of compilation errors, for example: > {code} > ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/helloworld2].[jsp]] (http-/127.0.0.1:8080-1) JBWEB000236: Servlet.service() for servlet jsp threw exception: org.apache.jasper.JasperException: JBWEB004062: Unable to compile class for JSP: > JBWEB004061: An error occurred at line: 32 in the generated java file > The code of method _jspService(HttpServletRequest, HttpServletResponse) is exceeding the 65535 bytes limit > JBWEB004211: Stacktrace: > at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:85) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4] > at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:69) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4] > at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:451) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4] > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[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 updated DROOLS-656: ------------------------------------ Description: 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 was: 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... 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 > 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.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-865) Setting transaction timeout on UserTransaction leaks to the thread and doesn't get cleared

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-865?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-865: ---------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 900984|https://bugzilla.redhat.com/show_bug.cgi?id=900984] from ON_QA to VERIFIED > Setting transaction timeout on UserTransaction leaks to the thread and doesn't get cleared > ------------------------------------------------------------------------------------------ > > Key: WFLY-865 > URL: https://issues.jboss.org/browse/WFLY-865 > Project: WildFly > Issue Type: Bug > Components: EE, Transactions > Reporter: jaikiran pai > Assignee: David Lloyd > > A user has reported (with an example) that setting a transaction timeout on the UserTransaction will leak the timeout onto the thread and subsequent transaction creation on that thread uses the leaked value instead of new values. > More details in the referenced forum thread. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-656) The blessed repo's should not accept a force push

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created DROOLS-656: --------------------------------------- Summary: The blessed repo's should not accept a 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... 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.8#6338)

11 years, 7 months

1
0
0 / 0

[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 updated DROOLS-656: ------------------------------------ Summary: The blessed repo's should not accept a git force push (was: The blessed repo's should not accept a force push) > 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... > 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.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-199) The entire kie build should move maven from 3.0.5 to 3.2.x

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-199?page=com.atlassian.jira.plugin... ] Geoffrey De Smet updated DROOLS-199: ------------------------------------ Description: Old description: To reproduce: - Install maven 3.1.0 - Run mvn-all.sh clean install -Dfull Note: Any changes to the pom must still allow them to run with 3.0.5 too. 1) At least droolsjbpm-tools (drools-eclipse) is guaranteed to fail because it uses an older tycho version and only tycho 0.18.1 is compatible with maven 3.1.0 according to the tycho mailing list. So the maven tycho plugin will need to be upgraded to 0.18.1 (which works with maven 3.0.5 too - so they say). 2) There might be other surprises... was: To reproduce: - Install maven 3.1.0 - Run mvn-all.sh clean install -Dfull Note: Any changes to the pom must still allow them to run with 3.0.5 too. 1) At least droolsjbpm-tools (drools-eclipse) is guaranteed to fail because it uses an older tycho version and only tycho 0.18.1 is compatible with maven 3.1.0 according to the tycho mailing list. So the maven tycho plugin will need to be upgraded to 0.18.1 (which works with maven 3.0.5 too - so they say). 2) There might be other surprises... > The entire kie build should move maven from 3.0.5 to 3.2.x > ---------------------------------------------------------- > > Key: DROOLS-199 > URL: https://issues.jboss.org/browse/DROOLS-199 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Critical > > Old description: > To reproduce: > - Install maven 3.1.0 > - Run mvn-all.sh clean install -Dfull > Note: Any changes to the pom must still allow them to run with 3.0.5 too. > 1) At least droolsjbpm-tools (drools-eclipse) is guaranteed to fail because it uses an older tycho version and only tycho 0.18.1 is compatible with maven 3.1.0 according to the tycho mailing list. > So the maven tycho plugin will need to be upgraded to 0.18.1 (which works with maven 3.0.5 too - so they say). > 2) There might be other surprises... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-199) The entire kie 6.3 build should move maven from 3.0.5 to 3.2.x

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-199?page=com.atlassian.jira.plugin... ] Geoffrey De Smet updated DROOLS-199: ------------------------------------ Summary: The entire kie 6.3 build should move maven from 3.0.5 to 3.2.x (was: The entire kie build should move maven from 3.0.5 to 3.2.x) > The entire kie 6.3 build should move maven from 3.0.5 to 3.2.x > -------------------------------------------------------------- > > Key: DROOLS-199 > URL: https://issues.jboss.org/browse/DROOLS-199 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Critical > > Old description: > To reproduce: > - Install maven 3.1.0 > - Run mvn-all.sh clean install -Dfull > Note: Any changes to the pom must still allow them to run with 3.0.5 too. > 1) At least droolsjbpm-tools (drools-eclipse) is guaranteed to fail because it uses an older tycho version and only tycho 0.18.1 is compatible with maven 3.1.0 according to the tycho mailing list. > So the maven tycho plugin will need to be upgraded to 0.18.1 (which works with maven 3.0.5 too - so they say). > 2) There might be other surprises... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-199) The entire kie build should work on maven 3.1.0 too

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-199?page=com.atlassian.jira.plugin... ] Geoffrey De Smet edited comment on DROOLS-199 at 11/26/14 8:58 AM: ------------------------------------------------------------------- @mbiarnes For kie 6.3, we should move to maven 3.2.x to avoid known issues in the very old maven version that we're using now. This means: - enforcing at least 3.2.3 (because 3.2.2 has a nasty bug) - notifying our developers in advance This doesn't apply to kie 6.2, because productization's infrastructure isn't ready. Productization (Julian) has been notified today that this will happen for kie 6.3, so they can prepare for this for 6.3. was (Author: ge0ffrey): @mbiarnes For kie 6.3, we should move to maven 3.2.x to avoid known issues in the very old maven version that we're using now. This means: - enforcing at least 3.2.3 (because 3.2.2 has a nasty bug) - notifying our developers in advance This doesn't apply to kie 6.2, because productization's infrastructure isn't ready. Productization has been warned today that this will happen for kie 6.3, so they can prepare for this for 6.3. > The entire kie build should work on maven 3.1.0 too > --------------------------------------------------- > > Key: DROOLS-199 > URL: https://issues.jboss.org/browse/DROOLS-199 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > > To reproduce: > - Install maven 3.1.0 > - Run mvn-all.sh clean install -Dfull > Note: Any changes to the pom must still allow them to run with 3.0.5 too. > 1) At least droolsjbpm-tools (drools-eclipse) is guaranteed to fail because it uses an older tycho version and only tycho 0.18.1 is compatible with maven 3.1.0 according to the tycho mailing list. > So the maven tycho plugin will need to be upgraded to 0.18.1 (which works with maven 3.0.5 too - so they say). > 2) There might be other surprises... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 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 November 2014