Felix Meschberger wrote: > Hi Agus, > > Agustín Gañán schrieb: >> Hi all, >> I'm working with the revision 734769 and I've detected an error when I try >> to install a bunlde from maven using the maven-sling-plugin. >> This is my plug-in config in the pom.xml [1] >> The bundle initializes content in the repository and this is the bundle's >> config [2]. >> And this is the error [3]: > > IIRC you might need to update the Felix Web Console to the latest > SNAPSHOT for this to work. > > If you don't need the latest feature of the sling plugin, you might want > to use version 2.0.2-incubator. This should work flawlessly. > > On the other hand, I think the plugin should better cope with the > situation, that the web console might not provide, what is required. > Carsten, WDYT ? > Hmm, ok, first, the release 2.0.2-incubator version and current trunk only differ in one functionality: automatically creating configurations for the file resource provider for initial content in an own project [1]. So unless you need this, use the released version :)
Then you can turn off the new feature, by "-Dsling.mountByFS=false" when invoking maven. Ok, now for handling this, I'm not sure - the current trunk requires a the latest trunk from the webconsole to work properly. I think, if the sling plugin is configured to add the configs it should fail if this isn't possible. So we could change the default if adding the configs to false, this should help in most cases and if someone explicitly turns on this feature, he knows what he does. We could also add a version check of the webconsole - so the sling plugin first sends a request to the webconsole requesting for the installed version and if the version is too low, it can give a better error message. So summarizing: We should - set the default to false for adding configs - add a version check of the web console WDYT? Carsten [1] https://issues.apache.org/jira/browse/SLING-798 -- Carsten Ziegeler [email protected]
