Hi,
As you already saw, there's a special classloader to handle embedding jars
into jars (which is in fact not standard).
There is (was?) a maven plugin called onejar-maven-plugin that would do
exactly that. This is a variant (currently offline so I can't double-check)
of the fatjar-maven-plugin.
Oh, I forgot to mention: I set up my pom so the classpath of my main
jar includes lib/, so all my users have to do is unzip it and run the
main jar.
On 6/12/13, Kevin Krumwiede wrote:
> As Anders Hammar said, there is some classpath magic to the way
> Eclipse creates executable jars containing ot
As Anders Hammar said, there is some classpath magic to the way
Eclipse creates executable jars containing other jars. I wanted
something like that, but instead I ended up creating an assembly that
creates a zip file. The zip file contains my main executable jar,
along with all the dependencies i
You only need to remove it from the name. The descriptor is perfectly fine.
On Jun 12, 2013, at 5:32 AM, Philippe Tjon-A-Hen wrote:
> I have the following pom.xml
>
> http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
> http://maven
I have the following pom.xml
http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
nl.tjonahen
reportbug
0.0.1-SNAPSHOT
Mix & Match
Mix & Ma
Jeff
http://mojo.codehaus.org/buildnumber-maven-plugin/usage.html
i would suggest putting the buildnumber into
inside the META-INF\manifest.mf
Martin
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht i
If you look closely, you will see that your first error is:
> [WARNING] Could not transfer metadata
> org.apache.maven.plugins/maven-metadata.xml from/to central
> (http://repo.maven.apache.org/maven2): Connection to
> http://repo.maven.apache.org refused
Given your corporate policy, I suspect
Currently, I am receiving errors indicating that there is a missing Maven
plugin and when the auto-download begins, I also receive an error that the
connection is refused. I know that connecting to external sources is
prohibited at my company, so I have been manually downloading and installing
> Wayne, I do the check and yes the dependency is inside the exec jar and
> yes inside that dependency I found the class AxisFault.class.
In that case, I cannot explain the error you seem to have run into.
Wayne
-
To unsubscribe
IIRC, there is no Java standard to put dependency JARs in a jar file. So I
believe there is some Eclipse magic (hence that file) to get that rolling.
/Anders
On Wed, Jun 12, 2013 at 9:59 PM, Jorge Infante Osorio wrote:
> Wayne, I do the check and yes the dependency is inside the exec jar and
>
Hi,
The Mojo team is pleased to announce the release of the
templating-maven-plugin version 1.0-alpha-3.
That project was designed to offer the Maven Right Way® :-) to filter
sources.
http://mojo.codehaus.org/templating-maven-plugin/
To get this update, simply specify the version in your projec
Wayne, I do the check and yes the dependency is inside the exec jar and yes
inside that dependency I found the class AxisFault.class.
When I ask about a class loader and put the eclipse example it´s because I see
this difference when compare the two jar, one generate by eclipse and the
another
Hi Eric,
> I'd like to convert the whole build to Maven, but am running into a
> wall trying to figure out how to create a project that needs no
> source, and packages with other projects' classes and resources.
The general approach to creating a JAR-with-dependencies or "uber-jar" is
to use eith
Hi,
I expect this information is available somewhere on the web and in searching
for it I've found vast amounts
of highly useful but completely non-relevant (to this problem) information.
Therefore I'm sending this email.
Hopefully, you can simply point me in the right direction with a quick e
Hi Jeff,
> is there a way to somehow use the buildNumber in the MANIFEST instead
> of the SNAPSHOT qualifier so we can easily see when troubleshooting
> which version is really deployed?
You can do something very close to what you want using the
buildnumber-maven-plugin. As Roy says, it will embe
You may be even more interested in injecting the version control tool's
code identification, like say the commit hash being built from git. Then
you can trace it back to the code directly!
Thanks,
Roy Lyons
On 6/12/13 1:17 PM, "Jeff" wrote:
>We have a continuous deployment system that con
> I double check and maven include this dependency inside the exec jar:
> axis2-1.6.1.wso2v6.jar
> and this dependency have org\apache\axis2\AxisFault.class
Unzip your jar file (or just drill into it) and see if that
AxisFault.class file is inside the jar you created.
> I could be a problem with
I have two jar, one created with eclipse and another with maven. Both have the
same dependencies but the one with maven have this error:
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/axis2/AxisFault
I double check and maven include this dependency inside the exec jar:
We have a continuous deployment system that constantly triggered by SCM
changes and builds/pushes our WAR files to our various environments.
I use the maven-war-plugin to insert specifics of the artifact into the
MANIFEST.MF. However, the version for SNAPSHOTs is always in the form
1.1.1-SNAPSHOT
> Now I see all the dependencies include inside my execute jar like Eclipse do
> it, but when I try it I see this error:
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/axis2/AxisFault
It seems you are missing a necessary dependency, thus the
NoClassDefFoundError you ra
Hi Anders.
I put this inside my pom.xml
org.apache.maven.plugins
maven-dependency-plugin
copy-dependencies
prepare-package
copy-dependencies
Greg,
When I said that the jar was not on the server, I meant that it's not part
of the JBoss AS 7 deployment, so it's not possible for it to be specified as
"provided". It's in my local repository (because I put it there) and clearly
needs to be packaged with my application. I think I've got it n
Hi Markus,
> How can I tell Maven that it must not rename the third party JAR when
> uploading it into Nexus
You cannot. One of the things that makes a Maven repository a Maven
repository is that it names things according to the Maven naming convention.
> to use the original third party file nam
Would an installer help resolve this?
Open source IzPack uses a maven plug-in to create an installation file
that could build the required structure on the user side from the
artifacts that you have.
Ron
On 11/06/2013 4:31 PM, James Green wrote:
Nexus is used to host the .exe file. As the ex
On Wed, Jun 12, 2013 at 7:17 AM, rdiddly wrote:
> Thanks Laird, that did the trick. BTW, I didn't specify the dependency in
> the
> EAR's pom. It's specified in the EJB-jar's pom and that dependency is
> apparently being picked up when building the EAR.
>
There you go. If it helps, my .ear file
Thanks Laird, that did the trick. BTW, I didn't specify the dependency in the
EAR's pom. It's specified in the EJB-jar's pom and that dependency is
apparently being picked up when building the EAR.
--
View this message in context:
http://maven.40175.n5.nabble.com/Using-Maven-to-produce-an-EAR-t
A clean build revealed many problems building the different artifacts due to
other small changes along the way. I'll have to do this more frequently as I
develop this mechanism. I have resolved each of those issues and you were
right, the jar got removed from the root. Next I will try the default l
2013/6/12 Stephen Connolly
> On 12 June 2013 11:04, Stephen Colebourne wrote:
>
> > I made this mistake too. Could I make some suggestions?
> >
> > Add the banned naming to the top of plugin guides, such as:
> > http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
> >
> >
> +
On 12 June 2013 11:04, Stephen Colebourne wrote:
> I made this mistake too. Could I make some suggestions?
>
> Add the banned naming to the top of plugin guides, such as:
> http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
>
>
+1, anyone want to take a stab at providing a p
you want to bind the dependency:copy-dependencies execution to the
`generate-resources` phase or at the latest the `prepare-package` phase...
though you may run into issues if you are using the common reactor for
generating the .exe and the .war (at least in the case where you use
lifecycle phases
I made this mistake too. Could I make some suggestions?
Add the banned naming to the top of plugin guides, such as:
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
Change this page to only have the single prefix-maven-plugin example:
http://maven.apache.org/guides/introdu
Stephen/Wayne,
I've got the maven-dependency-plugin to download and copy our .exe into
src/main/webapp just fine. However, with the package lifecycle, it fails to
make it into the web archive. If I switch it to the validate lifecycle, it
works.
I'm supposing the invocation is happening after the
Richard,
When a Java EE server deploys an application EAR, its various components are
categorised as modules:
Each EJB jar is a separate module
Each WAR is a separate module - including all of the jars in it's WEB-INF/lib
directory
All the jars in the EAR/lib directory are considered as a single
Stephen,
Many thanks for filing this - I do assure you that I was not under the
impression the GitHub plugin was official or even endorsed but I agree that
the trademark requires work to enforce. And I just love their response in
your ticket - made me laugh and cringe..!
James
On 11 June 2013 2
34 matches
Mail list logo
