The basic idea of modularity is not limited to software design. Indeed, modularity finds its inspiration in many natural and social phenomenae. Baldwin and Clark (1997) transfer the concept of modularity to management in an impactful research article published in the Harward Business Review (see Baldwin and Clark, 1997). They
See on citeulike [scribd id=34480234 key=key-3ovxl8rnmfjih5e80i4 mode=list]
[scribd id=34478392 key=key-8x3boagxgw4hk2vei84 mode=list]
Presentation: [scribd id=34478580 key=key-21sn08wa1esgm8aiekfq mode=list] Feedback Discussion: [scribd id=34478652 key=key-1gwjce8lem4dpweh2m0c mode=list]
Problem Eclipse won‘t compile a project, that is compiled by Maven without problems. The error message is: „Cannot find the class file for org.dom4j.io.XMLWriter“ Solution For me, it solved the problem to provide a bundle, which wraps the dom4j jar, and explicitly import the bundle „org.
Problem As I have written earlier, I copy the MANIFEST.MF, which is generated by the Maven Bundle Plugin into my eclipse PDE projects. The problem is that eclipse PDE has problems with picking up the contents of the newly created MANIFEST.MF. Solution One solution I have found is
In a previous post, I have provided an example of a possible Maven configuration to use the maven eclipse plugin with eclipse PDE. Besides these settings, which are the same for every project, each bundle needs to be configured as OSGi bundle in order to be usable by eclipse PDE.
pom.xml As noted on the Maven Eclipse plugin website, a two additional plugins need to be added to the project‘s pom. These copy the dependencies‘ jar files into the project folder and remove them on the eclipse:clean command. I found it helpful to add a further antrun
Problem When trying to use the Google Docs API inside an OSGi bundle, the following exception is thrown, for instance when trying to upload a document: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type application/atom+xml at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:877) at javax.activation.DataHandler.
Problem When attempting to serialize a bean, which uses property change support, XStream throws the following exepection. message : Cannot create java.beans.PropertyChangeSupport by JDK serialization : null cause-exception : com.thoughtworks.xstream.converters.reflection.ObjectAccessException Solution The only solution I found was to ignore the field pointing to the PropertyChangeSupport class
Problem When trying to package or install a project using the maven-bundle-plugin, an error message as the following is given: [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Cannot find lifecycle mapping for packaging: 'bundle'. Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingbundle.
Problem When creating eclipse meta-data with the maven-eclipse-plugin for plug-in projects, other related projects, which are part of the same eclipse workspace are not added to the project‘s classpath. Therewith, the project, although it compiles without problems in maven, shows syntax errors such as „[class] cannot be resolved“ and
