Announcement Announcement Module
Collapse
No announcement yet.
Incomplete spring.handlers/schemas after jar generation Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Incomplete spring.handlers/schemas after jar generation

    Hi,

    Im currently struggling with a jar-with-dependencies generation.
    The problem as the title says, my spring.handlers and spring.schemas are not complete which causes that some frameworks, especially spring-batch cannot find its handler...

    If my analyzis was right, when i run the maven package the building process takes the first spring.handlers and spring.schemas it meets (in my case they're those of spring-beans)
    After this and while navigating through dependencies, it skips the handlers and schemas of other dependencies... (spring-batch, spring-aop etc...) which is printed in the output while building :
    [INFO] META-INF/spring.handlers already added, skipping
    is this a normal behavior? in the end i find myself with a spring.handlers file containing only the content of that of spring-beans? shouldn't it append the content of the next spring.handlers files?

    Thanks in advance

  • #2
    Ok i fixed it with a workaround. i got some help from these pages:
    http://jira.codehaus.org/browse/MASSEMBLY-360
    http://blogs.woerd.de/roller/joerg/e...ring_and_maven

    but the fieldSet tag didn't work for me for a reason that i dont know.. and used instead the file tag to include the spring.handlers and spring.schemas directly into the META-INF.

    Neverthless, i had to make the concatenation manually of all the dependencies to obtain a valid handlers and schemas, but it's not a big deal since only some projects of spring contain them.

    Comment

    Working...
    X