Hi all, I was able to reproduce it and fix it ...
Looks like we need to modify the list of goals used by the Release plugin (when performing the release) from "<goals>deploy</goals>" to "<goals>install deploy</goals>" to have the dependencies in the jar... This is very weird but it works... I'll relaunch a vote for releasing a new version today. Thanks, Pierre-Arnaud On Thu, Oct 16, 2008 at 6:05 PM, Pierre-Arnaud Marcelot <[EMAIL PROTECTED]>wrote: > Hi Kiran, > > Actually, Emmanuel found the issue. The Apache DS dependencies are not > there... > I don't know why but Maven did not copy the dependencies when I released > the plugin. > Everything is well set up in the pom.xml and it works when I compile and > install the plugin (using mvn clean install) but for some reason it does not > work when releasing. > > I need to do more release test to see what's going on... But at least we > have the cause... > > Regards, > Pierre-Arnaud > > > On Thu, Oct 16, 2008 at 5:50 PM, Kiran Ayyagari <[EMAIL PROTECTED]>wrote: > >> hi Pierre, >> >> you are right, I saw this working when launched from IDE, this is odd, >> can this be due to any sort of missing >> dependency (which is not critical for running the studio but required >> for this functionality) >> >> Kiran Ayyagari >> >> Pierre-Arnaud Marcelot wrote: >> >>> Hi again Kiran, >>> >>> On Thu, Oct 16, 2008 at 2:23 PM, Pierre-Arnaud Marcelot <[EMAIL >>> PROTECTED]<mailto: >>> [EMAIL PROTECTED]>> wrote: >>> >>> I can confirm this. I dropped my ".ApacheDirectoryStudio" folder >>> and got this error. It was working fun when I did my testing >>> before the release... This is odd... >>> >>> >>> The strange thing is it's working if I launch Studio embedded in Eclipse >>> (with a launch configuration) but it doesn't in the RCP application... >>> >>> Pierre-Arnaud >>> >>> >> >> >
