You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "David Jencks (JIRA)" <ju...@ws.apache.org> on 2009/12/24 19:32:29 UTC
[jira] Updated: (JUDDI-299) start using the release plugin and
nexus
[ https://issues.apache.org/jira/browse/JUDDI-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated JUDDI-299:
-------------------------------
Attachment: JUDDI-299.diff
Attached patch uses apache-6 pom, and the apache-release profile. It also tries to add the console to the main build, which doesn't quite work, apparently due to a problem with the antrun plugin. I think that the antrun plugin can be replaced here with the assembly plugin configuration and possibly the dependency plugin.
I changed the judd-dist to use only the assembly plugin so the juddi-dist/build.xml can be removed. The juddi-dist build requires some artifacts from apache-release profile so I added it to that profile. Also it doesn't seem useful to push it to maven repos so I disabled deploy for it. Personally I don't see the need for this kind of dist with the default source distro from apache-release, but that's just my opinion.
My original reason for looking at this is that geronimo needs the juddi jars as osgi bundles, so that's part of the patch. I might need to update the maven-bundle-plugin configuration to get everything to work.
> start using the release plugin and nexus
> ----------------------------------------
>
> Key: JUDDI-299
> URL: https://issues.apache.org/jira/browse/JUDDI-299
> Project: jUDDI
> Issue Type: Task
> Reporter: Kurt T Stam
> Assignee: Kurt T Stam
> Fix For: 3.0.1
>
> Attachments: JUDDI-299.diff
>
>
> Just like we do for scout.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.