[jira] Closed: (SLING-120) Building microsling-standalone from its parent microsling directory fails

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-120.
----------------------------------

    Resolution: Won't Fix

As microsling is obsolete I'll close this bug.

> Building microsling-standalone from its parent microsling directory fails
> -------------------------------------------------------------------------
>
>                 Key: SLING-120
>                 URL: https://issues.apache.org/jira/browse/SLING-120
>             Project: Sling
>          Issue Type: Bug
>          Components: microsling
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>
> See the TODO in https://svn.apache.org/repos/asf/incubator/sling/trunk/microsling/pom.xml (revision 600989):
>  <modules>
>         <module>microsling-core</module>
>         <!-- 
>           TODO having this here should allow "mvn install" to first 
>           build microsling-core and then the assembly, but that 
>           doesn't work on my macosx / Maven 2.0.7 system: the 
>           assembly plugin looks for files in this directory,
>           instead of the microsling-standalone directory
>         <module>microsling-standalone</module>
>         -->
>     </modules>
> Not sure if there's something wrong in the POMs, or if this is a maven-assembly-plugin bug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.