[ http://jira.magnolia.info/browse/MAGNOLIA-1264?page=all ]

Grégory Joseph updated MAGNOLIA-1264:
-------------------------------------

          Summary: core and jcr serialization should be 100% independant of 
openwfe  (was: cleanup unwanted dependencies brought by openwfe in magnolia 
core)
      Component/s: core
    Fix Version/s: Orange
                       (was: 3.5 RC1)
      Description: 
the openwfe-jcr dependency in magnolia core is bringing a bunch of unwanted 
dependencies:

       org.openwfe:openwfe-jcr:jar:1.7.2pre15:compile
          ant:ant:jar:1.6.5:compile
          ant:ant-launcher:jar:1.6.5:compile
       org.openwfe:openwfe-applic:jar:1.7.2pre15:compile
          xml-apis:xml-apis:jar:1.0.b2:compile

both xml apis and ant should not be included, and also openwfe-applic looks a 
little bit overkilling.
If the openwfe-jcr is just needed for generic jcr "serialization" and not for 
workflow support (how it should), could we (John? Nico?) refactor such classes 
in a way that they are REALLY independent of openwfe and fix this?
I would like to remove anything belonging to the openwfe groupId in core (non 
because I don't like openwfe, but because workflow support should really be 
optional, and I assume that openwfe artifacts should only be related to 
workflow) :)




  was:
the openwfe-jcr dependency in magnolia core is bringing a bunch of unwanted 
dependencies:

       org.openwfe:openwfe-jcr:jar:1.7.2pre15:compile
          ant:ant:jar:1.6.5:compile
          ant:ant-launcher:jar:1.6.5:compile
       org.openwfe:openwfe-applic:jar:1.7.2pre15:compile
          xml-apis:xml-apis:jar:1.0.b2:compile

both xml apis and ant should not be included, and also openwfe-applic looks a 
little bit overkilling.
If the openwfe-jcr is just needed for generic jcr "serialization" and not for 
workflow support (how it should), could we (John? Nico?) refactor such classes 
in a way that they are REALLY indipendent of openwfe and fix this?
I would like to remove anything belonging to the openwfe groupId in core (non 
because I don't like openwfe, but because workflow support should really be 
optional, and I assume that openwfe artifacts should only be related to 
workflow) :)





> core and jcr serialization should be 100% independant of openwfe
> ----------------------------------------------------------------
>
>                 Key: MAGNOLIA-1264
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-1264
>             Project: Magnolia
>          Issue Type: Improvement
>          Components: core, deployment
>    Affects Versions: 3.0.1
>            Reporter: Fabrizio Giustina
>         Assigned To: Boris Kraft
>             Fix For: Orange
>
>
> the openwfe-jcr dependency in magnolia core is bringing a bunch of unwanted 
> dependencies:
>        org.openwfe:openwfe-jcr:jar:1.7.2pre15:compile
>           ant:ant:jar:1.6.5:compile
>           ant:ant-launcher:jar:1.6.5:compile
>        org.openwfe:openwfe-applic:jar:1.7.2pre15:compile
>           xml-apis:xml-apis:jar:1.0.b2:compile
> both xml apis and ant should not be included, and also openwfe-applic looks a 
> little bit overkilling.
> If the openwfe-jcr is just needed for generic jcr "serialization" and not for 
> workflow support (how it should), could we (John? Nico?) refactor such 
> classes in a way that they are REALLY independent of openwfe and fix this?
> I would like to remove anything belonging to the openwfe groupId in core (non 
> because I don't like openwfe, but because workflow support should really be 
> optional, and I assume that openwfe artifacts should only be related to 
> workflow) :)

-- 
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/docs/en/editor/stayupdated.html
----------------------------------------------------------------

Reply via email to