[ 
http://jira.magnolia.info/browse/MAGNOLIA-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gregory Joseph closed MAGNOLIA-1439.
------------------------------------

    Resolution: Won't Fix
      Assignee: Gregory Joseph  (was: Sameer Charles)

Please reopen if this occurs again, but I believe both the 3.0 and the 3.5 
branch are fine. We had a whole load of issues with the release plugin prior to 
3.5, but the branch and the pom you mention seem ok now.
http://svn.magnolia.info/view/community/magnolia/branches/magnolia-3.0/magnolia/pom.xml?revision=17576&view=markup


> Magnolia build to create a war builds using older release jars
> --------------------------------------------------------------
>
>                 Key: MAGNOLIA-1439
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-1439
>             Project: Magnolia
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0.3
>         Environment: Sun Java 1.5.0_10, Maven 2.0.5
>            Reporter: David Smith
>            Assignee: Gregory Joseph
>            Priority: Minor
>
> Magnolia subproject in the 3.0.x branch builds a war using older 3.0.2 jars 
> rather than the 3.0.x-SNAPSHOT jars just built in the local subprojects.  It 
> seems rather counter-intuitive to go through the process of building a .war 
> file from branch that doesn't actually use the branch jar files.  
> Dependencies in the magnolia subproject pom.xml should use the snapshot jars 
> built by the other subprojects.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to