Hey Carsten,
Okey, I will look for contributing a patch :).
The reason I would personally add the pom.xml is so that you know how the
archive was actually built, what dependencies it has, a name and description,
maybe some link to documentation to a github from the scm tags.
Greets,
Roy
> O
Roy Teeuwen wrote
> Hey Carsten,
>
> I had a look at the slingshot example that you set up with this. I see that a
> file slingstart.mar gets created, containing all the jars and model files
> that are necessary.
>
> Is there a reason that the name is always slingstart.mar, and not for example
Hey Carsten,
I had a look at the slingshot example that you set up with this. I see that a
file slingstart.mar gets created, containing all the jars and model files that
are necessary.
Is there a reason that the name is always slingstart.mar, and not for example
artifactId-version.mar? Or tha
Hi,
I've just added support to create an archive (jar file) with a
provisioning model and all the contained artifacts. Initially I thought
that we don't need this..but...
I used the slingshot sample project as a driver for this as that project
consists of a bundle and a provisioning model for the
