Look in META-INF/maven of the jars made with Maven, which should include a
copy of pom.xml. Then just make sure your project has an updated
block.
Now what could be interesting is to include the exact git commit at point
of packaging, which I believe could be possible to add using the release
Bundle is a special type used by the maven bundle plugin, which replaces
the normal jar with one augmented with OSGi metadata.
It is also possible to augment the replaced JAR further, e.g. shadow
classes from other dependencies.
When deployed, the result is still a *.jar, so it can be used as a
Sounds tricky, even if you get Maven and it's dependencies working with
James, presumably you would also need javac to compile?
Why do you want to compile Java code on the embedded platform?
It should be more doable to package your application for jamvm using Maven,
but doing that packaging on a
Yes, some years ago we did exactly this; most academic open source projects
then didn't bother with Maven Central and we relied on 8 different open
repositories around the world, often with dubious hostnames like
rpc268.cs.example.edu:8080 -- this meant that although the build was
reproducible for
gt; To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
--
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718
-
To unsubscribe, e-mail: users-unsubscr...@
+1 to ALLOW (but not require) the second use case of , this let you have autocomplete say in Eclipse's XML editor.
However I believe a xsi schemalocation would then still be needed per
plugin unless a catalogue is accessible out of bands, so it would still be
a bit verbose.
(I never understood
Hi,
license-maven-plugin is not maintained by Apache, and have its own mailing
list which should be able to help you further:
http://www.mojohaus.org/license-maven-plugin/mail-lists.html
Some documentation for each goal:
http://www.mojohaus.org/license-maven-plugin/plugin-info.html
On 26 May
in target/classes contains ${groupId}
and finally after running the archetype contains the user-provided
groupId.
On 16 May 2016 at 11:37, Stian Soiland-Reyes <st...@apache.org> wrote:
> Hi,
>
> We have a sub-module that is a Maven Archetype.
>
> Within the generated pom.x
obviously I can't just hard-code the version number in
archetypes.properties - as that would just
move the problem.
Any ideas?
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/-0001-9842-9718
