[magnolia-dev] [JIRA] (ARCH-37) Maven 2 will import the incorrect dependency

2014-08-07 Thread on behalf of Grégory Joseph














































Grégory Joseph
 updated  ARCH-37


Maven 2 will import the incorrect dependency
















Change By:


Grégory Joseph
(07/Aug/14 1:26 PM)




Component/s:


project



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (ARCH-37) Maven 2 will import the incorrect dependency

2014-08-05 Thread JIRA (on behalf of Peili Liang)














































Peili Liang
 created  ARCH-37


Maven 2 will import the incorrect dependency















Issue Type:


Bug



Assignee:


Joerg Bellmann



Created:


05/Aug/14 2:00 PM



Description:


We use archetype to create a project and a webapp (we select the magnolia-version: 5.3.1, and we change the dependency to ee-bundle after the project is created) but we can not start the create webapp. it will throw the following exception:


Aug 5, 2014 11:46:35 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.42
info.magnolia.module.model.reader.ModuleDependencyException: The following exceptions were found while checking Magnolia modules dependencies (i.e. those in META-INF/magnolia/my-module.xml):
Module Magnolia RSS Aggregator Module (version 2.3.1) is dependent on scheduler version 2.1.2/*, but Magnolia Scheduler Module (version 2.1.1) is currently installed.

2014-08-05 11:46:41,175 ERROR info.magnolia.init.MagnoliaServletContextListener : Oops, Magnolia could not be started
info.magnolia.module.model.reader.ModuleDependencyException: The following exceptions were found while checking Magnolia modules dependencies (i.e. those in META-INF/magnolia/my-module.xml):
Module Magnolia RSS Aggregator Module (version 2.3.1) is dependent on scheduler version 2.1.2/*, but Magnolia Scheduler Module (version 2.1.1) is currently installed.



The RSS module should depend the scheduler 2.1.2 in 5.3.1. but you will find the scheduler 2.1.1 is installed when you start the webapp.

	When I use Maven 3 and remove the two dependency(magnolia-project and magnolia-ui-project) in project pom file, as a result I can start the webapp correctly.
	When I use Maven2 and remove the two dependency(magnolia-project and magnolia-ui-project) in project pom file, as a result I can also start the webapp correctly.






Project:


Magnolia Maven Archetypes



Priority:


Neutral




Reporter:


Peili Liang




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (ARCH-37) Maven 2 will import the incorrect dependency

2014-08-05 Thread JIRA (on behalf of Peili Liang)














































Peili Liang
 updated  ARCH-37


Maven 2 will import the incorrect dependency
















Change By:


Peili Liang
(05/Aug/14 2:05 PM)




Description:


Weusearchetypetocreateaprojectandawebapp(weselectthemagnolia-version:5.3.1,andwechangethedependencytoee-bundleaftertheprojectiscreated)butwecannotstartthewebapp.itwillthrowthefollowingexception:{code:xml}Aug5,201411:46:35AMorg.apache.catalina.core.StandardEnginestartInternalINFO:StartingServletEngine:ApacheTomcat/7.0.42info.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.2014-08-0511:46:41,175ERRORinfo.magnolia.init.MagnoliaServletContextListener:Oops,Magnoliacouldnotbestartedinfo.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.{code}TheRSSmoduleshoulddependthescheduler2.1.2in5.3.1.butyouwillfindthescheduler2.1.1isinstalledwhenyoustartthewebapp.*WhenIuseMaven3andremovethetwodependency(magnolia-projectandmagnolia-ui-project)inprojectpomfile,asaresultIcanstartthewebappcorrectly.*WhenIuse
Maven2
Maven2
andremovethetwodependency(magnolia-projectandmagnolia-ui-project)inprojectpomfile,asaresultIcanalsostartthewebappcorrectly.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (ARCH-37) Maven 2 will import the incorrect dependency

2014-08-05 Thread JIRA (on behalf of Peili Liang)














































Peili Liang
 updated  ARCH-37


Maven 2 will import the incorrect dependency
















Change By:


Peili Liang
(05/Aug/14 2:04 PM)




Description:


Weusearchetypetocreateaprojectandawebapp(weselectthemagnolia-version:5.3.1,andwechangethedependencytoee-bundleaftertheprojectiscreated)butwecannotstartthe
create
webapp.itwillthrowthefollowingexception:{code:xml}Aug5,201411:46:35AMorg.apache.catalina.core.StandardEnginestartInternalINFO:StartingServletEngine:ApacheTomcat/7.0.42info.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.2014-08-0511:46:41,175ERRORinfo.magnolia.init.MagnoliaServletContextListener:Oops,Magnoliacouldnotbestartedinfo.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.{code}TheRSSmoduleshoulddependthescheduler2.1.2in5.3.1.butyouwillfindthescheduler2.1.1isinstalledwhenyoustartthewebapp.*WhenIuseMaven3andremovethetwodependency(magnolia-projectandmagnolia-ui-project)inprojectpomfile,asaresultIcanstartthewebappcorrectly.*WhenIuseMaven2andremovethetwodependency(magnolia-projectandmagnolia-ui-project)inprojectpomfile,asaresultIcanalsostartthewebappcorrectly.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (ARCH-37) Maven 2 will import the incorrect dependency

2014-08-05 Thread JIRA (on behalf of Cheng Hu)














































Cheng Hu
 updated  ARCH-37


Maven 2 will import the incorrect dependency
















Change By:


Cheng Hu
(05/Aug/14 2:10 PM)




Description:


*TheProblem*
Weusearchetypetocreateaprojectandawebapp(weselectthemagnolia-version:5.3.1,andwechangethedependencytoee-bundleaftertheprojectiscreated)butwecannotstartthewebapp.itwillthrowthefollowingexception:{code:xml}Aug5,201411:46:35AMorg.apache.catalina.core.StandardEnginestartInternalINFO:StartingServletEngine:ApacheTomcat/7.0.42info.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.2014-08-0511:46:41,175ERRORinfo.magnolia.init.MagnoliaServletContextListener:Oops,Magnoliacouldnotbestartedinfo.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.{code}TheRSSmoduleshoulddependthescheduler2.1.2in5.3.1.butyouwillfindthescheduler2.1.1isinstalledwhenyoustartthewebapp.*WhenIuseMaven3andremovethetwodependency(magnolia-projectandmagnolia-ui-project)inprojectpomfile,asaresultIcanstartthewebappcorrectly.*WhenIuseMaven2andremovethetwodependency(magnolia-projectandmagnolia-ui-project)inprojectpomfile,asaresultIcanalsostartthewebappcorrectly.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (ARCH-37) Maven 2 will import the incorrect dependency

2014-08-05 Thread JIRA (on behalf of Cheng Hu)














































Cheng Hu
 updated  ARCH-37


Maven 2 will import the incorrect dependency
















Change By:


Cheng Hu
(05/Aug/14 2:11 PM)




Description:


*TheProblem*
Weuse
Use
archetypetocreateaprojectandawebapp(weselectthemagnolia-version:5.3.1,andwechangethedependencytoee-bundleaftertheprojectiscreated)
butwecannotstartthewebapp
.
it
Thewebappcannotbestartedand
willthrowthefollowingexception:{code:xml}Aug5,201411:46:35AMorg.apache.catalina.core.StandardEnginestartInternalINFO:StartingServletEngine:ApacheTomcat/7.0.42info.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.2014-08-0511:46:41,175ERRORinfo.magnolia.init.MagnoliaServletContextListener:Oops,Magnoliacouldnotbestartedinfo.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.{code}TheRSSmoduleshoulddependthescheduler2.1.2in5.3.1.butyouwillfindthescheduler2.1.1isinstalledwhenyoustartthewebapp.*WhenIuseMaven3andremovethetwodependency(magnolia-projectandmagnolia-ui-project)inprojectpomfile,asaresultIcanstartthewebappcorrectly.*WhenIuseMaven2andremovethetwodependency(magnolia-projectandmagnolia-ui-project)inprojectpomfile,asaresultIcanalsostartthewebappcorrectly.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (ARCH-37) Maven 2 will import the incorrect dependency

2014-08-05 Thread JIRA (on behalf of Cheng Hu)














































Cheng Hu
 updated  ARCH-37


Maven 2 will import the incorrect dependency
















Change By:


Cheng Hu
(05/Aug/14 2:15 PM)




Description:


*TheProblem*Usearchetypetocreateaprojectandawebapp(weselectthemagnolia-version:5.3.1,andwechangethedependencytoee-bundleaftertheprojectiscreated).Thewebappcannotbestartedandwillthrowthefollowingexception:{code:xml}Aug5,201411:46:35AMorg.apache.catalina.core.StandardEnginestartInternalINFO:StartingServletEngine:ApacheTomcat/7.0.42info.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.2014-08-0511:46:41,175ERRORinfo.magnolia.init.MagnoliaServletContextListener:Oops,Magnoliacouldnotbestartedinfo.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.{code}
*
The
Cause*The
RSSmoduleshoulddependthe
{{
scheduler2.1.2
}}
in5.3.1.
Thefollowingclauseintheparent{{pom.xml}}oftheprojectcreatedbythearchetype,specificallythedependencyon{{magnolia-ui-project}}whichdependson{{scheduler2.1.1}}seemstocausingtheconflictinschedulerversions:{code:xml}!--DuetoabuginMaven2,wehavetoimportinfo.magnolia:magnolia-projecthere.Itwouldnormallynotbeneeded,sinceinfo.magnolia:magnolia-bundle-parentalreadyimportsit.(seebelow)Thedependencytoinfo.magnolia:magnolia-projectneedstobeBEFOREthedependencytoinfo.magnolia:magnolia-bundle-parent,otherwiseitdoesntworkeither.Alsonotethatthisisassumingmagnolia-projectandmagnolia-ui-projecthavethesameversionnumberasmagnolia-bundle-parent,whichnotalwaysbetrueinthefuture.IfyouareusingMaven3,youshouldnotneedthe2dependenciesbelow,andallshouldbewell.--dependencygroupIdinfo.magnolia/groupIdartifactIdmagnolia-project/artifactIdversion${magnoliaVersion}/versiontypepom/typescopeimport/scope/dependencydependencygroupIdinfo.magnolia.ui/groupIdartifactIdmagnolia-ui-project/artifactIdversion${magnoliaVersion}/versiontypepom/typescopeimport/scope/dependency{code}*PossibleSolutions*
butyouwillfindthescheduler2.1.1isinstalledwhenyoustartthewebapp.*WhenIuseMaven3andremovethetwodependency(magnolia-projectandmagnolia-ui-project)inprojectpomfile,asaresultIcanstartthewebappcorrectly.*WhenIuseMaven2andremovethetwodependency(magnolia-projectandmagnolia-ui-project)inprojectpomfile,asaresultIcanalsostartthewebappcorrectly.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (ARCH-37) Maven 2 will import the incorrect dependency

2014-08-05 Thread JIRA (on behalf of Cheng Hu)














































Cheng Hu
 updated  ARCH-37


Maven 2 will import the incorrect dependency
















Change By:


Cheng Hu
(05/Aug/14 2:20 PM)




Description:


*TheProblem*Usearchetypetocreateaprojectandawebapp(weselectthemagnolia-version:5.3.1,andwechangethedependencytoee-bundleaftertheprojectiscreated).Thewebappcannotbestartedandwillthrowthefollowingexception:{code:xml}Aug5,201411:46:35AMorg.apache.catalina.core.StandardEnginestartInternalINFO:StartingServletEngine:ApacheTomcat/7.0.42info.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.2014-08-0511:46:41,175ERRORinfo.magnolia.init.MagnoliaServletContextListener:Oops,Magnoliacouldnotbestartedinfo.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.{code}*TheCause*TheRSSmoduleshoulddependthe{{scheduler2.1.2}}in5.3.1.Thefollowingclauseintheparent{{pom.xml}}oftheprojectcreatedbythearchetype,specificallythedependencyon{{magnolia-ui-project}}whichdependson{{scheduler2.1.1}}seemstocausingtheconflictinschedulerversions:{code:xml}!--DuetoabuginMaven2,wehavetoimportinfo.magnolia:magnolia-projecthere.Itwouldnormallynotbeneeded,sinceinfo.magnolia:magnolia-bundle-parentalreadyimportsit.(seebelow)Thedependencytoinfo.magnolia:magnolia-projectneedstobeBEFOREthedependencytoinfo.magnolia:magnolia-bundle-parent,otherwiseitdoesntworkeither.Alsonotethatthisisassumingmagnolia-projectandmagnolia-ui-projecthavethesameversionnumberasmagnolia-bundle-parent,whichnotalwaysbetrueinthefuture.IfyouareusingMaven3,youshouldnotneedthe2dependenciesbelow,andallshouldbewell.--dependencygroupIdinfo.magnolia/groupIdartifactIdmagnolia-project/artifactIdversion${magnoliaVersion}/versiontypepom/typescopeimport/scope/dependencydependencygroupIdinfo.magnolia.ui/groupIdartifactIdmagnolia-ui-project/artifactIdversion${magnoliaVersion}/versiontypepom/typescopeimport/scope/dependency{code}*PossibleSolutions**Ifwemake{{magnolia-ui-project}}dependon{{scheduler2.1.2}},thewebappwillbuildandrun*IfweuseMaven3anddeletetheabove,thewebappwillbuildandrun*IfweuseMaven2anddeletetheabove,thewebappstillbuildsandruns*Question**
(?)
Whyistheaboveclauseinthepomnecessary
(
?
)




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (ARCH-37) Maven 2 will import the incorrect dependency

2014-08-05 Thread JIRA (on behalf of Cheng Hu)














































Cheng Hu
 updated  ARCH-37


Maven 2 will import the incorrect dependency
















Change By:


Cheng Hu
(05/Aug/14 2:20 PM)




Description:


*TheProblem*Usearchetypetocreateaprojectandawebapp(weselectthemagnolia-version:5.3.1,andwechangethedependencytoee-bundleaftertheprojectiscreated).Thewebappcannotbestartedandwillthrowthefollowingexception:{code:xml}Aug5,201411:46:35AMorg.apache.catalina.core.StandardEnginestartInternalINFO:StartingServletEngine:ApacheTomcat/7.0.42info.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.2014-08-0511:46:41,175ERRORinfo.magnolia.init.MagnoliaServletContextListener:Oops,Magnoliacouldnotbestartedinfo.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.{code}*TheCause*TheRSSmoduleshoulddependthe{{scheduler2.1.2}}in5.3.1.Thefollowingclauseintheparent{{pom.xml}}oftheprojectcreatedbythearchetype,specificallythedependencyon{{magnolia-ui-project}}whichdependson{{scheduler2.1.1}}seemstocausingtheconflictinschedulerversions:{code:xml}!--DuetoabuginMaven2,wehavetoimportinfo.magnolia:magnolia-projecthere.Itwouldnormallynotbeneeded,sinceinfo.magnolia:magnolia-bundle-parentalreadyimportsit.(seebelow)Thedependencytoinfo.magnolia:magnolia-projectneedstobeBEFOREthedependencytoinfo.magnolia:magnolia-bundle-parent,otherwiseitdoesntworkeither.Alsonotethatthisisassumingmagnolia-projectandmagnolia-ui-projecthavethesameversionnumberasmagnolia-bundle-parent,whichnotalwaysbetrueinthefuture.IfyouareusingMaven3,youshouldnotneedthe2dependenciesbelow,andallshouldbewell.--dependencygroupIdinfo.magnolia/groupIdartifactIdmagnolia-project/artifactIdversion${magnoliaVersion}/versiontypepom/typescopeimport/scope/dependencydependencygroupIdinfo.magnolia.ui/groupIdartifactIdmagnolia-ui-project/artifactIdversion${magnoliaVersion}/versiontypepom/typescopeimport/scope/dependency{code}

*PossibleSolutions*
butyouwillfindthe
*Ifwemake{{magnolia-ui-project}}dependon{{
scheduler2.1.
1isinstalledwhenyoustart
2}},
thewebapp
.
willbuildandrun
*
WhenI
Ifwe
useMaven3and
remove
delete
the
twodependency(magnolia-projectandmagnolia-ui-project)inprojectpomfile
above
,
asaresultIcanstart
thewebapp
correctly.
willbuildandrun
*
WhenI
Ifwe
useMaven2and
remove
delete
the
twodependency(magnolia-projectandmagnolia-ui-project)inprojectpomfile
above
,
asaresultIcanalsostart
thewebapp
correctly.
stillbuildsandruns*Question**Whyistheaboveclauseinthepomnecessary(?)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (ARCH-37) Maven 2 will import the incorrect dependency

2014-08-05 Thread JIRA (on behalf of Cheng Hu)














































Cheng Hu
 updated  ARCH-37


Maven 2 will import the incorrect dependency
















Change By:


Cheng Hu
(05/Aug/14 2:21 PM)




Description:


*TheProblem*Usearchetypetocreateaprojectandawebapp(weselectthemagnolia-version:5.3.1,andwechangethedependencytoee-bundleaftertheprojectiscreated).Thewebappcannotbestartedandwillthrowthefollowingexception:

{code:xml}Aug5,201411:46:35AMorg.apache.catalina.core.StandardEnginestartInternalINFO:StartingServletEngine:ApacheTomcat/7.0.42info.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.2014-08-0511:46:41,175ERRORinfo.magnolia.init.MagnoliaServletContextListener:Oops,Magnoliacouldnotbestartedinfo.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.{code}*TheCause*TheRSSmoduleshoulddependthe{{scheduler2.1.2}}in5.3.1.Thefollowingclauseintheparent{{pom.xml}}oftheprojectcreatedbythearchetype,specificallythedependencyon{{magnolia-ui-project}}whichdependson{{scheduler2.1.1}}seemstocausingtheconflictinschedulerversions:{code:xml}!--DuetoabuginMaven2,wehavetoimportinfo.magnolia:magnolia-projecthere.Itwouldnormallynotbeneeded,sinceinfo.magnolia:magnolia-bundle-parentalreadyimportsit.(seebelow)Thedependencytoinfo.magnolia:magnolia-projectneedstobeBEFOREthedependencytoinfo.magnolia:magnolia-bundle-parent,otherwiseitdoesntworkeither.Alsonotethatthisisassumingmagnolia-projectandmagnolia-ui-projecthavethesameversionnumberasmagnolia-bundle-parent,whichnotalwaysbetrueinthefuture.IfyouareusingMaven3,youshouldnotneedthe2dependenciesbelow,andallshouldbewell.--dependencygroupIdinfo.magnolia/groupIdartifactIdmagnolia-project/artifactIdversion${magnoliaVersion}/versiontypepom/typescopeimport/scope/dependencydependencygroupIdinfo.magnolia.ui/groupIdartifactIdmagnolia-ui-project/artifactIdversion${magnoliaVersion}/versiontypepom/typescopeimport/scope/dependency{code}*PossibleSolutions**Ifwemake{{magnolia-ui-project}}dependon{{scheduler2.1.2}},thewebappwillbuildandrun*IfweuseMaven3anddeletetheabove,thewebappwillbuildandrun*IfweuseMaven2anddeletetheabove,thewebappstillbuildsandruns*Question**(?)Whyistheaboveclauseinthepomnecessary?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (ARCH-37) Maven 2 will import the incorrect dependency

2014-08-05 Thread JIRA (on behalf of Cheng Hu)














































Cheng Hu
 updated  ARCH-37


Maven 2 will import the incorrect dependency
















Change By:


Cheng Hu
(05/Aug/14 2:24 PM)




Description:


*TheProblem*Usearchetypetocreateaprojectandawebapp(weselectthemagnolia-version:5.3.1,andwechangethedependencytoee-bundleaftertheprojectiscreated).Thewebappcannotbestartedandwillthrowthefollowingexception:{code:xml}Aug5,201411:46:35AMorg.apache.catalina.core.StandardEnginestartInternalINFO:StartingServletEngine:ApacheTomcat/7.0.42info.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.2014-08-0511:46:41,175ERRORinfo.magnolia.init.MagnoliaServletContextListener:Oops,Magnoliacouldnotbestartedinfo.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.{code}*TheCause*TheRSSmoduleshoulddependthe{{scheduler2.1.2}}in5.3.1.Thefollowingclauseintheparent{{pom.xml}}oftheprojectcreatedbythearchetype,specificallythedependencyon{{magnolia-ui-project}}whichdependson{{scheduler2.1.1}}seemstocausingtheconflictinschedulerversions:{code:xml}!--DuetoabuginMaven2,wehavetoimportinfo.magnolia:magnolia-projecthere.Itwouldnormallynotbeneeded,sinceinfo.magnolia:magnolia-bundle-parentalreadyimportsit.(seebelow)Thedependencytoinfo.magnolia:magnolia-projectneedstobeBEFOREthedependencytoinfo.magnolia:magnolia-bundle-parent,otherwiseitdoesntworkeither.Alsonotethatthisisassumingmagnolia-projectandmagnolia-ui-projecthavethesameversionnumberasmagnolia-bundle-parent,whichnotalwaysbetrueinthefuture.IfyouareusingMaven3,youshouldnotneedthe2dependenciesbelow,andallshouldbewell.--dependencygroupIdinfo.magnolia/groupIdartifactIdmagnolia-project/artifactIdversion${magnoliaVersion}/versiontypepom/typescopeimport/scope/dependencydependencygroupIdinfo.magnolia.ui/groupIdartifactIdmagnolia-ui-project/artifactIdversion${magnoliaVersion}/versiontypepom/typescopeimport/scope/dependency{code}*PossibleSolutions**Ifwe
copywhatisdoneintheee-bundle,wecanaddthefollowingdependencytotheparentpom.xmlandthewebappwillbuildandrun{code:xml}dependencygroupIdinfo.magnolia/groupIdartifactIdmagnolia-module-scheduler/artifactIdversion2.1.2/version/dependency{code}*Ifwe
make{{magnolia-ui-project}}dependon{{scheduler2.1.2}},thewebappwillbuildandrun*IfweuseMaven3anddeletetheabove,thewebappwillbuildandrun*IfweuseMaven2anddeletetheabove,thewebappstillbuildsandruns*Question**(?)Whyistheaboveclauseinthepomnecessary?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (ARCH-37) Maven 2 will import the incorrect dependency

2014-08-05 Thread JIRA (on behalf of Cheng Hu)














































Cheng Hu
 updated  ARCH-37


Maven 2 will import the incorrect dependency
















Change By:


Cheng Hu
(05/Aug/14 2:29 PM)




Description:


*TheProblem*Usearchetypetocreateaprojectandawebapp(weselectthemagnolia-version:5.3.1,andwechangethedependencytoee-bundleaftertheprojectiscreated).Thewebappcannotbestartedandwillthrowthefollowingexception:{code:xml}Aug5,201411:46:35AMorg.apache.catalina.core.StandardEnginestartInternalINFO:StartingServletEngine:ApacheTomcat/7.0.42info.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.2014-08-0511:46:41,175ERRORinfo.magnolia.init.MagnoliaServletContextListener:Oops,Magnoliacouldnotbestartedinfo.magnolia.module.model.reader.ModuleDependencyException:ThefollowingexceptionswerefoundwhilecheckingMagnoliamodulesdependencies(i.e.thoseinMETA-INF/magnolia/my-module.xml):ModuleMagnoliaRSSAggregatorModule(version2.3.1)isdependentonschedulerversion2.1.2/*,butMagnoliaSchedulerModule(version2.1.1)iscurrentlyinstalled.{code}*TheCause*TheRSSmoduleshoulddependthe{{scheduler2.1.2}}in5.3.1.Thefollowingclauseintheparent{{pom.xml}}oftheprojectcreatedbythearchetype,specificallythedependencyon{{magnolia-ui-project}}whichdependson{{scheduler2.1.1}}seemstocausingtheconflictinschedulerversions:{code:xml}!--DuetoabuginMaven2,wehavetoimportinfo.magnolia:magnolia-projecthere.Itwouldnormallynotbeneeded,sinceinfo.magnolia:magnolia-bundle-parentalreadyimportsit.(seebelow)Thedependencytoinfo.magnolia:magnolia-projectneedstobeBEFOREthedependencytoinfo.magnolia:magnolia-bundle-parent,otherwiseitdoesntworkeither.Alsonotethatthisisassumingmagnolia-projectandmagnolia-ui-projecthavethesameversionnumberasmagnolia-bundle-parent,whichnotalwaysbetrueinthefuture.IfyouareusingMaven3,youshouldnotneedthe2dependenciesbelow,andallshouldbewell.--dependencygroupIdinfo.magnolia/groupIdartifactIdmagnolia-project/artifactIdversion${magnoliaVersion}/versiontypepom/typescopeimport/scope/dependencydependencygroupIdinfo.magnolia.ui/groupIdartifactIdmagnolia-ui-project/artifactIdversion${magnoliaVersion}/versiontypepom/typescopeimport/scope/dependency{code}*PossibleSolutions**Ifwecopywhatisdoneintheee-bundle,wecanaddthefollowingdependencytotheparentpom.xmlandthewebappwillbuildandrun{code:xml}dependencygroupIdinfo.magnolia/groupIdartifactIdmagnolia-module-scheduler/artifactIdversion2.1.2/version/dependency{code}*Ifwemake{{magnolia-ui-project}}dependon{{scheduler2.1.2}},thewebappwillbuildandrun*IfweuseMaven3anddeletetheabove,thewebappwillbuildandrun*IfweuseMaven2anddeletetheabove,thewebappstillbuildsandruns*Question**(?)Whyistheaboveclauseinthepomnecessary?
WhatistheMaven2bug?




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (ARCH-37) Maven 2 will import the incorrect dependency

2014-08-05 Thread on behalf of Grégory Joseph














































Grégory Joseph
 updated  ARCH-37


Maven 2 will import the incorrect dependency
















Hey Peili,

The Maven issue only manifests itself when your local maven repo doesn't have the parent poms yet. To check it out: find ~/.m2/repository/info  -name parent -or -name project  -exec rm -rvf {} \;





Change By:


Grégory Joseph
(05/Aug/14 6:43 PM)




Fix Version/s:


1.2.1



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com