[
https://issues.apache.org/jira/browse/JUDDI-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks reopened JUDDI-361:
--------------------------------
This change makes the artifact not be a bundle, so I hope we can find a better
solution.
I'm very confused by all the antrun and include/exclude configuration in the
pom. Can you describe what the code is trying to do? Maybe there's a simpler
way.
Why is *-persistence.xml copied to anywhere in the src directory (this is
normally a terrible idea) and why is it copied at all if it isn't included in
the output jar?
I think that the <include-Resource> instruction can be used to include the
startup data and that perhaps defining resources in the hibernate and openjpa
profiles can be used to avoid the need to copy anything.
> Bundle packaging ignoring the JAR plugin excludes
> -------------------------------------------------
>
> Key: JUDDI-361
> URL: https://issues.apache.org/jira/browse/JUDDI-361
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.2
> Reporter: Tom Cunningham
> Assignee: Tom Cunningham
> Fix For: 3.0.2
>
>
> The bundle plugin seems to be causing the JAR excludes not to fire.
> Adding a <goal>jar</goal> to the executions seems to fix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
