+1 for this bug Packaging 'jar' is also skipped, even if its the project where mvn pax:provision is run from.
Sometimes we need to use 'jar' (i.e. non-bundle) packaging to do workarounds because of the sometimes non-compatibility of 'bundle' (see http://jira.codehaus.org/browse/MEVENIDE-653 for example) On Mon, Jul 21, 2008 at 12:45 AM, Ulrik Sandberg (JIRA) < [EMAIL PROTECTED]> wrote: > pax:provision does not include local project if its of packaging 'war' > ---------------------------------------------------------------------- > > Key: PAXCONSTRUCT-89 > URL: http://issues.ops4j.org/jira/browse/PAXCONSTRUCT-89 > Project: Pax Construct > Issue Type: Bug > Components: maven-pax-plugin > Affects Versions: 1.3 > Reporter: Ulrik Sandberg > Assignee: Stuart McCulloch > > > Changed a local (generated) bundle project from packaging 'bundle' to > 'war', and then pax:provision didn't deploy it. Had to explicitly specify > the artifact with -DdeployURL. > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://issues.ops4j.org/jira/secure/Administrators.jspa > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- Best regards, Hendy Irawan
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
