[ http://issues.apache.org/jira/browse/JCR-332?page=comments#action_12426170 ] Christoph Kiehl commented on JCR-332: -------------------------------------
Jukka, I my case the problem were the newlines of the multiline description. Plexus archiver adds a line break after a certain amount of characters. Somehow I ended up with a manifest that contained an empty line which is not allowed by specification. One could probably try to adjust the line length in the description to avoid this, but that way it gets really fragile against changes. Just try to build the jcr-rmi jar and look at your manifest. > maven2 pom contribution > ----------------------- > > Key: JCR-332 > URL: http://issues.apache.org/jira/browse/JCR-332 > Project: Jackrabbit > Issue Type: New Feature > Components: maven > Affects Versions: 1.0, 1.0.1, 0.9 > Reporter: fabrizio giustina > Assigned To: Jukka Zitting > Priority: Minor > Fix For: 1.1 > > Attachments: jackrabbit-core_single-line-description_pom.xml.patch, > jackrabbit-jcr-rmi_single-line-description-and-rmic_pom.xml.patch, > jcr-rmi-pom.xml, pom.xml, pom.xml, pom.xml.patch > > > If you are interested in migrating to maven2 (or adding optional maven 2 > build scripts) this is a full maven 2 pom.xml for the main jackrabbit jar. > All the xpath/javacc stuff, previously done in maven.xml, was pretty painfull > to reproduce in maven2... the attached pom exactly reproduces the m1 build by > using the maven2 javacc plugin + a couple of antrun executions. > Test configuration is not yet complete, I think it will be a lot better to > reproduce the previous behaviour (init tests run first) without any > customization (maybe using a single junit test suite with setUp tasks). Also > custom packaging goals added to maven.xml (that can be esily done in m2 by > using the assembly plugin) are not yet reproduced too. > If there is interest, I can also provide poms for the contribution projects > (that will be easy, the only complex pom is the main one). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
