[MGNLEE-143] magnolia_control.sh file is not set to executable in bundle Created: 05/Jun/09  Updated: 23/Jun/14  Resolved: 08/Jun/09

Status: Closed
Project: Magnolia DX Core
Component/s: None
Affects Version/s: None
Fix Version/s: 4.1, 4.0.2

Type: Bug Priority: Major
Reporter: Boris Kraft Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MAGNOLIA-2770 magnolia_control.sh file is not set t... Closed
supersession
is superseded by BUILD-15 Update to maven-assembly-plugin 2.2-b... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

see:

BKMacBook:bin boriskraft$ ls -F
bootstrap.jar setclasspath.bat
catalina-tasks.xml setclasspath.sh*
catalina.bat shutdown.bat
catalina.sh* shutdown.sh*
commons-daemon.jar startup.bat
commons-logging-api-1.1.1.jar startup.sh*
cpappend.bat tomcat-juli.jar
digest.bat tomcat-native.tar.gz
digest.sh* tomcat5.exe
jkstatus-tasks.xml tomcat5w.exe
jmxaccessor-tasks.xml tool-wrapper.bat
jsvc.tar.gz tool-wrapper.sh*
magnolia_control.bat version.bat
magnolia_control.sh version.sh*



 Comments   
Comment by Magnolia International [ 05/Jun/09 ]

This is most likely due to a bug in the assembly plugin. With the parent pom v9, we updated to 2.2-beta-3, where this bug was introduced, and fixed in 2.2-beta-4, which was released just recently.

See http://jira.codehaus.org/browse/MASSEMBLY-238

Comment by Magnolia International [ 08/Jun/09 ]

fixed in trunk and 4.0 branch

Generated at Mon Feb 12 05:27:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.