[deepamehta-devel] Maven repository
jucovschi at gmail.com
Sun Aug 31 19:00:05 CEST 2014
One must follow the instructions from
http://central.sonatype.org/pages/ossrh-guide.html. I think the best
would be if somebody from DeepaMehta core team would create the JIRA
account. With this account, one can create and remove releases.
I don't think I've seen nightly builds in Central. I would only put
stable(-ish) releases there. The release process per-se is automatic.
If you want, you can upload previous releases but I would personally
not spend too much time on that.
The archetype approach is very handy indeed. I think the easiest way
to do development is to create a project using one of the archetypes.
Build it once and make a symlink from the jar to the deploy directory
of DM karaf
distribution. This works like hot deployment. I don't think it works
on windows though.
On Sun, Aug 31, 2014 at 1:36 AM, Jörg Richter <jri at deepamehta.de> wrote:
> Hi Constantin,
>> I could not find the URL where DeepaMehta maven artifacts are stored.
> The DM Maven repo is here:
>> I would be happy to help uploading DeepaMehta on maven central.
> That's great! You could possibly make the contact to the Central people (or whatever procedure is required) at then provide me with the credentials for the file upload (if any are required). I would setup our CI (Jenkins) then to let it upload the nightly builds as well as the releases to Central. My idea is to have this upload process completely automated.
> Uploading the previous releases might require some manual work. It would be great if you can help here too. You'll find the previous released bundles in the DM Maven repo (see above). For a complete archive of released DM distributions see http://download.deepamehta.de/archive/ (The current release is directly at http://download.deepamehta.de)
>> This will have an immediate benefit that developers don't have to recompile DeepaMehta on their computer before being able to create their first plugin. Plus it improves the installation process.
> DM developer Danny pursues a similar approach. His DM4 Archetypes project allows a developer to start a DM plugin project from scratch, that is with nothing else but a cloned DM4 Archetypes repo. The DM4 Archetypes pull in all required artifacts from the DM Maven repo and provides you templates(=archetypes) for several DM plugin types. See the READMEs of the several provided archetypes.
> However, what the dev environment setup by DM4 Archetypes does not provide is hot deployment. Hot deployment means that DM automatically redeploys a bundle once it is compiled and build. This is a very handy feature while plugin development. Currently the only way to get a hot deployment environment is to build DM from source.
> devel mailing list
> devel at lists.deepamehta.de
More information about the devel