Closed ghost closed 9 years ago
@patricklwy14 - it's not clear to me from your report, but are you using the AEM developer tools for Eclipse when deploying?
I'm using eclipse luna JEE version, having AEM Dev Tools 1.0.4 plugin installed for development. I then use my Terminal command prompt to run the maven command (mvn clean install -PautoInstallBundle) to deploy.
Right, but do you deploy using the AEM Dev Tools?
I guess nope...cause essentially it's only maven command, right?
I chance upon some forum mentioning that if the bundle version is the same, it won't get updated unless the version number ended with -SNAPSHOT. Could it be the root cause here?
I chance upon some forum mentioning that if the bundle version is the same, it won't get updated unless the version number ended with -SNAPSHOT
That's right, please use -SNAPSHOT for your Maven artifact version.
Arggss..!!! OSGI Bundle...! Thanks for the prompt response guys!
Cool, happy to help
From the main project directory, run cmd = mvn clean install -PautoInstallBundle for the first time. Bundle deploy successfully.
Do some changes like add new classes, new methods in existing class and update the version in package-info.java. Run the same command again and it indicate BUILD SUCCESS from the command prompt.
What's observed:
Using JDK 1.7.0_75, with Maven 3.2.5 in OSX Yosemite.